Skip to content

Add npm package version override capability #30302

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

trishume
Copy link
Contributor

@trishume trishume commented May 8, 2025

For enterprises which use an internal NPM repo to limit package installations to approved versions, the behavior of always looking for the actual latest version means that functionality like Github Copilot breaks. This provides the ability to pin packages like the copilot LSP to specific approved versions so they keep working.

Release Notes:

  • N/A

@cla-bot cla-bot bot added the cla-signed The user has signed the Contributor License Agreement label May 8, 2025
@trishume
Copy link
Contributor Author

trishume commented May 9, 2025

In a messaging discussion we determined that it's also possible to fix this issue by using the system node, except that doesn't work because PATH is read too early, before it's initialized from the system PATH. So this may not be necessary.

@trishume trishume closed this May 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla-signed The user has signed the Contributor License Agreement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants