84f4d2630f
This partially reverts https://github.com/zed-industries/zed/pull/3324 We will still blank out user/global config when running managed NPM, to keep to the spirit of #3324 (which was made at the time we did not allow user-provided NPM builds - the intent of the change was to make the behavior of NPM as consistent as possible). I tested this change by: 1. Setting up a custom NPM registry via Versaccio 2. Adding this new registry to my .npmrc 3. Mirroring `vscode-langservers-extracted` to it 4. Blocking access to `registry.npmjs.org` 5. Opening up settings.json file in Zed Nightly - Verifying that language server update fails for it 6. Opening up Zed Dev build of this branch - Confirming that language server update check goes through for it Closes #19806 Closes #20749 Closes #9422 Release Notes: - User and global .npmrc configuration is now respected when running user-provided NPM binary (which also happens automatically when `npm` from PATH is newer than 18.0.0) |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||
| LICENSE-GPL | ||