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.

Sign up for GitHub

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

Jump to bottom

pnpm should prefer npmRegistry config instead of global npm config #737

Closed

coolyuantao opened this issue Sep 28, 2023 · 1 comment · Fixed by #751

coolyuantao commented Sep 28, 2023 •

edited

Loading

To configure the server, I create a config.json file then pass it to the server bootstrap command.

  "npmRegistry": "http://npm.xxxx.cn",

But I found that when pnpm install packages, it bypassed the npmRegistry config and directly used the global registry config.

As a result, the packages in the private npm registry could not be loaded correctly. The solution can only be achieved by modifying the global registry config.

Is it a bug or a feature?

The text was updated successfully, but these errors were encountered:

Member

ije commented Sep 28, 2023

i guess it's kind of a bug, the npmRegistry in config.json has higher priority

edeustace added a commit to ahum/esm.sh that referenced this issue


          fix: write npmrc file if NpmRegistry is set fixes esm-dev#737

6a5975f

edeustace mentioned this issue

fix: write npmrc file if NpmRegistry is set - fixes #737 #751

Merged

ije closed this as completed in #751

ije pushed a commit that referenced this issue


          fix: write npmrc file if NpmRegistry is set fixes #737 (#751)

8b0300b

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment