Repository navigation
tsp install ignores user .npmrc #11665
Description
Repro Steps
- create a user .npmrc pointing to an alternative package registry
- run "tsp install"
Expected: Respects user .npmrc
Actual: Ignores user .npmrc, tries to fetch from npmjs.org
Also appears to ignore NPM_CONFIG_REGISTRY env var:
% export NPM_CONFIG_REGISTRY=...
% npx tsp install --debug
trace cli.args: CLI args: { _: [ 'install' ], debug: true, pretty: true, '$0': 'tsp' }
Internal compiler error!
File issue at https://github.com/microsoft/typespec
[TypeError: fetch failed] {
[cause]: Error: read ENOTCONN
at TLSWrap.onStreamRead (node:internal/stream_base_commons:216:20) {
errno: -57,
code: 'ENOTCONN',
syscall: 'read'
}
}
Reacted by github-actions and Copilot
Activity
github-actions commentedon Aug 14, 2026
🎯 Issue Triage
tsp installdoes not respect the user-level.npmrcfile, causing it to always fetch packages from the default npmjs.org registry instead of any configured alternative registry.Category: Bug
Area:
compiler:core🔍 Analysis
tsp installinvokes npm under the hood to install TypeSpec dependencies. The issue is that the npm invocation may be ignoring the user-level~/.npmrcor project-level.npmrcthat specifies an alternative registry.tsp installeither uses a hardcoded registry URL, passes--registryexplicitly, or spawns npm in a way that bypasses the standard.npmrclookup.packages/compiler— thetsp installCLI command implementation.📝 Suggested next steps
tsp installimplementation inpackages/compilerand check how npm is invoked--registryflag or environment variable is being hardcoded.npmrc(e.g., do not override registry).npmrcregistry configuration is honoredDisable e2e tests (#11687)
timotheeguerin commentedon Aug 27, 2026
So the problem with respecting .npmrc and NPM_CONFIG_REGISTRY is that typespec is package manager agnostic. Doing a bit of research other packages managers do not usually respect the
NPM_CONFIG_REGISTRYvar and have their own. As for npmrc it is a bit more but yarn 2+ doesn't respect it either.In practice
tsp installjust install the configured package manager(similar to how corepack did it) and run the install command for it(delegating to its own install logic). So you should need the TYPESPEC_NPM_REGISTRY env + whatever package manager you use config but after that everything should work. I am a bit more reluctant to change that right now without any strong ask..npmrcregistryNPM_CONFIG_REGISTRYPNPM_CONFIG_REGISTRY.yarnrc.ymlYARN_NPM_REGISTRY_SERVERBUN_CONFIG_REGISTRYCOREPACK_NPM_REGISTRYSupport registry mirrors in tsp install (microsoft#11776)