pnpm doesn't get packages from expected registry

[uiolee]

Verify latest release

• I verified that the issue exists in the latest pnpm release

pnpm version

8.14.1

Which area(s) of pnpm are affected? (leave empty if unsure)

CLI

Link to the code that reproduces this issue or a replay of the bug

No response

Reproduction steps

reproduction sample: #7542 (comment)

1. pnpm config set registry https://registry.npmjs.org/ [--location project] (default registry)
2. pnpm init
3. pnpm i eslint (or any other packages.)
4. pnpm config set registry https://localhost:56341/ [--location project] (specify any registry you want)
5. pnpm add a_packages
   (pnpm will try to download packages from npmjs instead of custom registry. It will get failed because the package doesn't exist in npmjs)

I am expected that pnpm should get packages from the custom registry instead of npmjs.com

Describe the Bug

after exec pnpm config set registry, pnpm add <pkg> doen't work as expected.

BTW: if you add, modify or delete packages in (dev)dependencies of packages.json, pnpm i get failed too.

BTW: this issue exist in monorepo too: if you add new packages to monorepo_worksplace(packages/*/) and run pnpm i, you will get failed too.

I guess it's related to node_modules/.modules.yaml, it keeps a registries item. Sometimes pnpm will update registries from .npmrc, but sometimes not. That's so weird, isn't it?

Expected Behavior

pnpm should get packages from the custom registry
pnpm should recognize the registry setting in .npmrc

Which Node.js version are you using?

v20.10.0

Which operating systems have you used?

• macOS
• Windows
• Linux

If your OS is a Linux based, which one it is? (Include the version if relevant)

No response

[weyert]

Did you add the config to point your scope to your private registry?

[uiolee]

sure

[nachoaldamav]

Can you try using using the .npmrc file? If it works this way it's a bug in pnpm config set.
https://pnpm.io/npmrc#registry--authentication-settings

[weyert]

Yeah, also seems like pnpm config set registry https://registry.npmjs.org/ seems to set it globally instead for the current directory 🤔 Not sure if that is caused by asdf

[uiolee]

Yes. .npmrc is correct. but it seems pnpm doesn't follow .npmrc

use pnpm config set ... --location project will get the same issue.

1. default setting

$ pnpm config set registry https://registry.npmjs.org/

$ cat $HOME/.npmrc
strict-ssl=false
registry=https://registry.npmjs.org/

2. init project

$ pwd
/d/git/tmp

$ ls -a
.  ..

$ pnpm init
Wrote to D:\git\tmp\package.json

{
  "name": "tmp",
  "version": "0.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": ""
}

$ pnpm i eslint
Packages: +99
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 99, reused 99, downloaded 0, added 99, done

dependencies:
+ eslint 8.56.0

Done in 4.7s

3. switch registry

$ pnpm config set registry https://private.registry.cccom/

$ cat $HOME/.npmrc
strict-ssl=false
registry=https://private.registry.cccom/

$ pnpm add a_packages
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/a_packages: Not Found - 404

I am expected that pnpm should get pkgs from the custom registry instead of npmjs.com

---

3. switch registry (project)

$ pnpm config set registry https://private.registry.cccom/ --location project

$ cat ./.npmrc
registry=https://private.registry.cccom/

$ pnpm add a_packages
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/a_packages: Not Found - 404

I am expected that pnpm should get pkgs from the custom registry instead of npmjs.com

[zkochan]

It was probably fixed by this: #7515

but not published yet.

[uiolee]

It was probably fixed by this: #7515

but not published yet.

I test via pd in latest main, it works as expected.

[taoliujun]

same problem.