[bug]: unable to install platform-specific `unrs-resolver` in internal registry

[hainenber]

Hi folks,

I had an issue when installing Jest v30 with logs shown below. The context is that my company employs an internal npm registry with proper authentication from env vars in project-wide .npmrc.

However, nabapi-postinstall script cannot install the platform-specific unrs-resolver as I believe due to auth token not being utilized.

Logs

info  build - npm error code 1
info  build - npm error path /home/vsts/work/1/s/node_modules/unrs-resolver
info  build - npm error command failed
info  build - npm error command sh -c napi-postinstall unrs-resolver 1.9.0 check
info  build - npm error [napi-postinstall@0.2.4] Trying to install package "@unrs/resolver-binding-linux-x64-gnu" using npm
info  build - npm error [napi-postinstall@0.2.4] Failed to install package "@unrs/resolver-binding-linux-x64-gnu" using npm Command failed: npm install --loglevel=error --prefer-offline --no-audit --progress=false @unrs/resolver-binding-linux-x64-gnu@1.9.0
info  build - npm error npm error code E401
info  build - npm error npm error Incorrect or missing password.
info  build - npm error npm error If you were trying to login, change your password, create an
info  build - npm error npm error authentication token or enable two-factor authentication then
info  build - npm error npm error that means you likely typed your password in incorrectly.
info  build - npm error npm error Please try again, or recover your password at:
info  build - npm error npm error   https://www.npmjs.com/forgot
info  build - npm error npm error
info  build - npm error npm error If you were doing some other operation then your saved credentials are
info  build - npm error npm error probably out of date. To correct this please try logging in again with:
info  build - npm error npm error   npm login
info  build - npm error npm error A complete log of this run can be found in: /home/app/.npm/_logs/2025-06-20T08_22_43_084Z-debug-0.log
info  build - npm error
info  build - npm error [napi-postinstall@0.2.4] Trying to download "[https://internal.npm.repositories.cloud/artifactory/api/npm/build.releases.npm/@unrs/resolver-binding-linux-x64-gnu/-/resolver-binding-linux-x64-gnu-1.9.0.tgz"](https://internal.npm.repositories.cloud/artifactory/api/npm/build.releases.npm/@unrs/resolver-binding-linux-x64-gnu/-/resolver-binding-linux-x64-gnu-1.9.0.tgz%22)
info  build - npm error [napi-postinstall@0.2.4] Failed to download "[https://internal.npm.repositories.cloud/artifactory/api/npm/build.releases.npm/@unrs/resolver-binding-linux-x64-gnu/-/resolver-binding-linux-x64-gnu-1.9.0.tgz"](https://internal.npm.repositories.cloud/artifactory/api/npm/build.releases.npm/@unrs/resolver-binding-linux-x64-gnu/-/resolver-binding-linux-x64-gnu-1.9.0.tgz%22) Server responded with 401
info  build - npm error /home/vsts/work/1/s/node_modules/napi-postinstall/lib/index.js:233
info  build - npm error                     throw new Error((0, helpers_js_1.errorMessage)(`Failed to install package "${pkg}"`, (0, helpers_js_1.getErrorMessage)(err)));
info  build - npm error                           ^
info  build - npm error
info  build - npm error Error: [napi-postinstall@0.2.4] Failed to install package "@unrs/resolver-binding-linux-x64-gnu": Server responded with 401
info  build - npm error     at checkAndPreparePackage (/home/vsts/work/1/s/node_modules/napi-postinstall/lib/index.js:233:27)
info  build - npm error     at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
info  build - npm error
info  build - npm error Node.js v22.12.0

[JounQin]

1. Are you using npm v10-?
2. Can you upgrade to npm v11?
3. I'm not sure why the following fails if .npmrc is already present at project level?

npm install --loglevel=error --prefer-offline --no-audit --progress=false @unrs/resolver-binding-linux-x64-gnu@1.9.0

So how is your .npmrc organized?

[m-szyszka]

Hi!
I have the same problem in my Azure DevOps pipeline.
Project has .npmrc file, and pipeline is organised that way:

- task: npmAuthenticate@0
        inputs:
          workingFile: '$(app_dir)/.npmrc'
        condition: eq(variables.NPMRCEXISTS, 'true')

...

- script: |
          npm config set script-shell '/bin/bash'
          npm install -g npm
          npm install || exit
          npm run build || exit
          npm run lint:report || exit

It was working well before recent upgrade to "jest" 30, which needs "unrs-resolver", which needs "napi-postinstall".
Error is:

Node.js v20.19.4
[napi-postinstall@0.3.2] Trying to install package "@unrs/resolver-binding-linux-x64-gnu" using npm
[napi-postinstall@0.3.2] Failed to install package "@unrs/resolver-binding-linux-x64-gnu" using npm Command failed: npm install --loglevel=error --prefer-offline --no-audit --progress=false @unrs/resolver-binding-linux-x64-gnu@1.11.1
npm error code E401
npm error Unable to authenticate, your authentication token seems to be invalid.
npm error To correct this please try logging in again with:
npm error   npm login
npm error A complete log of this run can be found in: /home/vsts/.npm/_logs/2025-07-24T14_08_57_405Z-debug-0.log

[napi-postinstall@0.3.2] Trying to download "[https://<FEED>/npm/registry/@unrs/resolver-binding-linux-x64-gnu/-/resolver-binding-linux-x64-gnu-1.11.1.tgz"](https://<FEED>/npm/registry/@unrs/resolver-binding-linux-x64-gnu/-/resolver-binding-linux-x64-gnu-1.11.1.tgz%22)
[napi-postinstall@0.3.2] Failed to download "[https://<FEED>/npm/registry/@unrs/resolver-binding-linux-x64-gnu/-/resolver-binding-linux-x64-gnu-1.11.1.tgz"](https://<FEED>/npm/registry/@unrs/resolver-binding-linux-x64-gnu/-/resolver-binding-linux-x64-gnu-1.11.1.tgz%22) Server responded with 401
/home/vsts/work/1/s/<APP>/node_modules/napi-postinstall/lib/index.js:234
                    throw new Error((0, helpers_js_1.errorMessage)(`Failed to install package "${pkg}"`, (0, helpers_js_1.getErrorMessage)(err)));
                          ^

Error: [napi-postinstall@0.3.2] Failed to install package "@unrs/resolver-binding-linux-x64-gnu": Server responded with 401
    at checkAndPreparePackage (/home/vsts/work/1/s/<APP>/node_modules/napi-postinstall/lib/index.js:234:27)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

I think it's because that addidional npm install --loglevel=error --prefer-offline --no-audit --progress=false @unrs/resolver-binding-linux-x64-gnu@1.11.1 doesn't use authentication scope from previous pipeline task.

What we can do with this issue?

[JounQin]

No one answered my question:

So how is your .npmrc organized?

The npm install command is executed at

napi-postinstall/src/index.ts

Lines 132 to 137 in 35b8970

	execSync(
	`npm install --loglevel=error --prefer-offline --no-audit --progress=false${
	isWasm32Wasi ? ` --cpu=${WASM32} --force` : ''
	} ${pkg}@${version}`,
	{ cwd: installDir, stdio: 'pipe', env },
	)

which is under <projectDir>/node_modules/unrs-resolver/npm-install dir, which should inherit using project level .npmrc automatically AFAIK.

---

Edit: https://docs.npmjs.com/cli/v8/configuring-npm/npmrc#files

It seems <projectDir>/node_modules/unrs-resolver/npm-install won't use <projectDir>/.npmrc automatically, @hainenber @m-szyszka could you try https://github.com/ds300/patch-package by copying .npmrc into <projectDir>/node_modules/unrs-resolver/npm-install to ensure this behavior?

[hainenber]

Sorry, I missed your reply.

1. I used npm v10 but the issue still persists after npm v11.
2. I couldn't do the patch-package because node_modules is not populated due to the napi-install issue

[JounQin]

I couldn't do the patch-package

I don't understand, I'm saying to patch napi-postinstall before https://github.com/un-ts/napi-postinstall/blob/35b89703ca70bcac381ddb7d6a3b04968fd36d1e/src/index.ts.

[hainenber]

Sorry for late revert but I downgraded back to Jest v29.7 since patch-package is unwelcomed in our org.

[JounQin]

@hainenber I'm just asking for testing the solution with patch-package, not proposaling a long term solution. If you want to resolve the issue, we need your testing here.

[hainenber]

unfortunately, patching unrs-resolver after adding.npmrc with my org's private registry config didn't work. I tried to patch the .npmrc to even napi-postinstall to take advantage of this LoC but to no avail.

https://github.com/un-ts/napi-postinstall/blob/main/src/helpers.ts#L11

I'm open for more experiments if needed, btw. Just with some delays, mind you.

[RemiBou]

I was able to overcome it by copying the .npmrc to the home
cp .npmrc $HOME/.npmrc

[koolshams]

I have similar issue. The npmrc file looks like this.

registry=https://artifactory.xxx/xxx/
//artifactory.xxx:_authToken=${TOKEN}

and we use `TOKEN=xxx npm ci

Now i see it is doing npm install again, my guess is the either npmrc is not read or TOKEN env variable is not passed down.
I also tried with npm 11 and tried with hardcoding TOKEN in npmrc instead of using env variable still throwing 401 error.

We did a temporary fix like this. add the following in npmrc

registry=https://artifactory.xxx/xxx/
@unrs:registry=https://registry.npmjs.org/
....

Uninstalled and installed jest to update package-lock. Now at least it works. But we do not want to use npm registry directly but to use artifactory pull through cache.