[BUG] Custom Registry with extended path does not work with version 11.3.0

[trauty-is-me]

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

The company I work for hosts our own NPM registry at https://example.domain.com/content/repositories/npmjs/

With version 11.2.0 and earlier running npm config set registry https://example.domain.com/content/repositories/npmjs/ allows packages to be installed.

With version 11.3.0 after running the above command it npm install attempts to fetch packages from https://example.domain.com/PATH_TO_PACKAGE instead of https://example.domain.com/content/repositories/npmjs/PATH_TO_PACKAGE

Expected Behavior

Install packages from path specified in npm config set registry

Steps To Reproduce

These steps assume you have a npm registry configured with a non root endpoint

1. Install NPM version 11.3.0
2. npm config set-registry https://example.domain.com/content/repositories/npmjs/
3. npm install

NPM install returns a 404 as it is attempting to pull the package from https://example.domain.com/PATH_TO_PACKAGE instead of https://example.domain.com/content/repositories/npmjs/PATH_TO_PACKAGE

Environment

• npm: 11.3.0
• Node.js: 22.14.0
• OS Name: Oracle Linux
• System Model Name: OL8-Slim
• npm config:

;#24 1.145 ; "user" config from /root/.npmrc
#24 1.145 
#24 1.145 registry = "https://example.domain.com/content/repositories/npmjs/"
#24 1.145 
#24 1.145 ; node bin location = /usr/local/bin/node
#24 1.145 ; node version = v22.14.0
#24 1.145 ; npm local prefix = /app
#24 1.145 ; npm version = 11.3.0
#24 1.145 ; cwd = /app
#24 1.145 ; HOME = /root
#24 1.145 ; Run `npm config ls -l` to show all defaults. ```

(Taken from Docker Build) and removed company internal registry from domain

[milaninfy]

It's working for me as expected. Check from the logs.
@trauty-is-me Can you please share your npm command run log like npm install --loglevel silly to check what's going on ?

~ $ npm -v
11.3.0

~/workarea/rep/test $ npm config set registry https://example.domain.com/content/repositories/npmjs/
~/workarea/rep/test $ npm config get registry
https://example.domain.com/content/repositories/npmjs/

~/workarea/rep/test $ npm install underscore --loglevel silly
npm verbose cli /Users/milaninfy/.nvm/versions/node/v22.14.0/bin/node /Users/milaninfy/.nvm/versions/node/v22.14.0/bin/npm
npm info using npm@11.3.0
npm info using node@v22.14.0
npm silly config load:file:/Users/milaninfy/.nvm/versions/node/v22.14.0/lib/node_modules/npm/npmrc
npm silly config load:file:/Users/milaninfy/workarea/rep/test/.npmrc
npm silly config load:file:/Users/milaninfy/.npmrc
npm silly config load:file:/Users/milaninfy/.nvm/versions/node/v22.14.0/etc/npmrc
npm verbose title npm install underscore
npm verbose argv "install" "underscore" "--loglevel" "silly"
npm verbose logfile logs-max:10 dir:/Users/milaninfy/.npm/_logs/2025-04-09T12_38_20_280Z-
npm verbose logfile /Users/milaninfy/.npm/_logs/2025-04-09T12_38_20_280Z-debug-0.log
npm silly logfile start cleaning logs, removing 1 files
npm silly packumentCache heap:4345298944 maxSize:1086324736 maxEntrySize:543162368
npm silly logfile done cleaning log files
npm silly idealTree buildDeps
npm silly fetch manifest underscore@*
npm silly packumentCache full:https://example.domain.com/content/repositories/npmjs/underscore cache-miss
npm http fetch GET https://example.domain.com/content/repositories/npmjs/underscore attempt 1 failed with ENOTFOUND
npm http fetch GET https://example.domain.com/content/repositories/npmjs/underscore attempt 2 failed with ENOTFOUND
⠸^C

[Xeroxxx]

I can confirm this issue. We've exactly the same behavior with Docker Images.

@milaninfy
Use an existing project with a package.json. npm install package does not trigger this behavior in my case.

[milaninfy]

@Xeroxxx if you are able to consistently reproduce this error on docker, can you share the reproduction case/steps where it's reproducible?

[Xeroxxx]

@milaninfy I'm not able to share any code, but I can describe this on a high level as there is no magic.

• We use Docker Images with latest NodeJS. We set the registry to internal repository (pull-through like nexus3) and "npm install npm@latest". Thats it image built.
• This image is used by the developers. They copy their project to /folder (WORKDIR /folder) and RUN npm install. NPM picksup the package.json

Boom, 404:

NPM install returns a 404 as it is attempting to pull the package from https://example.domain.com/PATH_TO_PACKAGE instead of https://example.domain.com/content/repositories/npmjs/PATH_TO_PACKAGE

[panga]

My organization have the same issue in 11.3.0 while using a private registry (artifactory). I can't provide reproduction steps at the moment.

[milaninfy]

@panga @Xeroxxx does 11.2.0 works without any issue ?

[Xeroxxx]

@milaninfy Yes it does.

[milaninfy]

I am assuming it's something like this.

# Build test-reg as builder from Node.js LTS with the latest npm and custom registry
FROM node:lts AS builder

# Update npm to the latest version
RUN npm install -g npm@latest

# Set custom npm registry
RUN npm config set registry https://example.domain.com/content/repositories/npmjs/

FROM builder

WORKDIR /app

RUN npm init -y
RUN npm -v
RUN npm install lodash -ddd

Docker run logs which shows it picks up the correct value from registry

#0 building with "desktop-linux" instance using docker driver

#1 [internal] load build definition from Dockerfile
#1 transferring dockerfile: 408B done
#1 DONE 0.0s

#2 [internal] load metadata for docker.io/library/node:lts
#2 DONE 0.4s

#3 [internal] load .dockerignore
#3 transferring context: 2B done
#3 DONE 0.0s

#4 [builder 1/3] FROM docker.io/library/node:lts@sha256:e5ddf893cc6aeab0e5126e4edae35aa43893e2836d1d246140167ccc2616f5d7
#4 CACHED

#5 [builder 2/3] RUN npm install -g npm@latest
#5 5.150 
#5 5.150 removed 14 packages, and changed 60 packages in 5s
#5 5.150 
#5 5.150 25 packages are looking for funding
#5 5.150   run `npm fund` for details
#5 DONE 5.2s

#6 [builder 3/3] RUN npm config set registry https://example.domain.com/content/repositories/npmjs/
#6 DONE 0.3s

#7 [stage-1 1/4] WORKDIR /app
#7 DONE 0.0s

#8 [stage-1 2/4] RUN npm init -y
#8 0.212 Wrote to /app/package.json:
#8 0.212 
#8 0.212 {
#8 0.212   "name": "app",
#8 0.212   "version": "1.0.0",
#8 0.212   "description": "",
#8 0.212   "main": "index.js",
#8 0.212   "scripts": {
#8 0.212     "test": "echo \"Error: no test specified\" && exit 1"
#8 0.212   },
#8 0.212   "keywords": [],
#8 0.212   "author": "",
#8 0.212   "license": "ISC",
#8 0.212   "type": "commonjs"
#8 0.212 }
#8 0.212 
#8 0.212 
#8 0.212 
#8 DONE 0.2s

#9 [stage-1 3/4] RUN npm -v
#9 0.118 11.3.0
#9 DONE 0.1s

#10 [stage-1 4/4] RUN npm install lodash -ddd
#10 0.095 npm verbose cli /usr/local/bin/node /usr/local/bin/npm
#10 0.095 npm info using npm@11.3.0
#10 0.095 npm info using node@v22.14.0
#10 0.095 npm silly config load:file:/usr/local/lib/node_modules/npm/npmrc
#10 0.095 npm warn -ddd is not a valid single-hyphen cli flag and will be removed in the future
#10 0.095 npm silly config load:file:/app/.npmrc
#10 0.095 npm silly config load:file:/root/.npmrc
#10 0.095 npm silly config load:file:/usr/local/etc/npmrc
#10 0.097 npm verbose title npm install lodash
#10 0.097 npm verbose argv "install" "lodash" "--loglevel" "silly"
#10 0.097 npm verbose logfile logs-max:10 dir:/root/.npm/_logs/2025-04-09T19_14_58_468Z-
#10 0.099 npm verbose logfile /root/.npm/_logs/2025-04-09T19_14_58_468Z-debug-0.log
#10 0.190 npm silly logfile done cleaning log files
#10 0.197 npm silly packumentCache heap:521404416 maxSize:130351104 maxEntrySize:65175552
#10 0.206 npm silly idealTree buildDeps
#10 0.207 npm silly fetch manifest lodash@*
#10 0.207 npm silly packumentCache full:https://example.domain.com/content/repositories/npmjs/lodash cache-miss
#10 0.245 npm http fetch GET https://example.domain.com/content/repositories/npmjs/lodash attempt 1 failed with ENOTFOUND
#10 10.26 npm http fetch GET https://example.domain.com/content/repositories/npmjs/lodash attempt 2 failed with ENOTFOUND
#10 CANCELED
ERROR: failed to solve: Canceled: context canceled

[jamonation]

Is something in this commit eating the custom portion of a registry path and returning undefined in some scenarios?

885accd#diff-2c1b7fd57f53b55bedbf1e56b4192b500e57d8a8e22b804b79278ce6cc0bd31aR835-R850

[Xeroxxx]

I am assuming it's something like this.

# Build test-reg as builder from Node.js LTS with the latest npm and custom registry
FROM node:lts AS builder

# Update npm to the latest version
RUN npm install -g npm@latest

# Set custom npm registry
RUN npm config set registry https://example.domain.com/content/repositories/npmjs/

FROM builder

WORKDIR /app

COPY /myapp /app

RUN npm init -y
RUN npm -v
RUN npm install lodash -ddd

npm install

Docker run logs which shows it picks up the correct value from registry

Kind of. Its separate images and as mentioned it only doesn't work with a package.json and npm install.

Installing random packages via npm install works fine.

[trauty-is-me]

Try this for replication, I needed to find a package with no dependancies to make the log small:

Dockerfile

FROM container-registry.oracle.com/os/oraclelinux:8-slim

RUN microdnf install npm nodejs gzip
RUN npm config set registry https://repository.example.com/content/repositories/npmjs/
RUN npm install -g n
RUN n stable
RUN npm install -g npm@11.3.0
COPY package*.json .
RUN npm install --loglevel silly

This for package.json

{
  "name": "foo",
  "version": "1.0.0",
  "main": "index.js",
  "scripts": {},
  "author": "",
  "license": "MIT",
  "description": "",
  "dependencies": {
    "rightpad": "^1.0.1"
  }
}

This give the following output when running docker build .

 => ERROR [8/8] RUN npm install --loglevel silly                                                                                                                                             6.4s
------                                                                                                                                                                                            
 > [8/8] RUN npm install --loglevel silly:                                                                                                                                                        
0.697 npm verbose cli /usr/local/bin/node /usr/local/bin/npm                                                                                                                                      
0.697 npm info using npm@11.3.0                                                                                                                                                                   
0.697 npm info using node@v22.14.0                                                                                                                                                                
0.697 npm silly config load:file:/usr/local/lib/node_modules/npm/npmrc
0.697 npm silly config load:file:/.npmrc
0.697 npm silly config load:file:/root/.npmrc
0.697 npm silly config load:file:/usr/local/etc/npmrc
0.699 npm verbose title npm install
0.699 npm verbose argv "install" "--loglevel" "silly"
0.699 npm verbose logfile logs-max:10 dir:/root/.npm/_logs/2025-04-10T06_33_14_780Z-
0.702 npm verbose logfile /root/.npm/_logs/2025-04-10T06_33_14_780Z-debug-0.log
1.188 npm silly logfile done cleaning log files
1.237 npm silly packumentCache heap:4345298944 maxSize:1086324736 maxEntrySize:543162368
1.250 npm silly idealTree buildDeps
1.253 npm silly reify moves {}
1.255 npm silly audit bulk request { rightpad: [ '1.0.1' ] }
1.261 npm http cache rightpad@https://repository.example.com/rightpad/-/rightpad-1.0.1.tgz 0ms (cache hit)
1.263 npm silly tarball no local data for rightpad@https://repository.example.com/rightpad/-/rightpad-1.0.1.tgz. Extracting by manifest.
5.000 npm http fetch POST 401 https://repository.example.com/content/repositories/npmjs/-/npm/v1/security/advisories/bulk 3744ms
5.001 npm verbose audit error HttpErrorAuthUnknown: Unable to authenticate, need: BASIC realm="Sonatype Nexus Repository Manager"
5.001 npm verbose audit error     at /usr/local/lib/node_modules/npm/node_modules/npm-registry-fetch/lib/check-response.js:88:17
5.001 npm verbose audit error     at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
5.001 npm verbose audit error     at async [getReport] (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/audit-report.js:294:19)
5.001 npm verbose audit error     at async AuditReport.run (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/audit-report.js:106:19) {
5.001 npm verbose audit error   headers: [Object: null prototype] {
5.001 npm verbose audit error     date: [ 'Thu, 10 Apr 2025 06:33:11 GMT' ],
5.001 npm verbose audit error     server: [ 'Nexus/2.15.2-03' ],
5.001 npm verbose audit error     'cache-control': [ 'private, max-age=0, must-revalidate' ],
5.001 npm verbose audit error     'x-frame-options': [ 'SAMEORIGIN' ],
5.001 npm verbose audit error     'x-content-type-options': [ 'nosniff' ],
5.001 npm verbose audit error     'www-authenticate': [ 'BASIC realm="Sonatype Nexus Repository Manager"' ],
5.001 npm verbose audit error     'content-length': [ '0' ],
5.001 npm verbose audit error     'strict-transport-security': [ 'max-age=63072000' ],
5.001 npm verbose audit error     'x-fetch-attempts': [ '1' ]
5.001 npm verbose audit error   },
5.001 npm verbose audit error   statusCode: 401,
5.001 npm verbose audit error   code: 'E401',
5.001 npm verbose audit error   method: 'POST',
5.001 npm verbose audit error   uri: 'https://repository.example.com/content/repositories/npmjs/-/npm/v1/security/advisories/bulk',
5.001 npm verbose audit error   body: <Buffer >,
5.001 npm verbose audit error   pkgid: 'bulk'
5.001 npm verbose audit error }
5.001 npm silly audit error
5.001 npm silly audit report null
6.389 npm http fetch GET 404 https://repository.example.com/rightpad/-/rightpad-1.0.1.tgz 5125ms (cache skip)
6.395 npm verbose stack HttpErrorGeneral: 404 Not Found - GET https://repository.example.com/rightpad/-/rightpad-1.0.1.tgz
6.395 npm verbose stack     at /usr/local/lib/node_modules/npm/node_modules/npm-registry-fetch/lib/check-response.js:103:15
6.395 npm verbose stack     at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
6.395 npm verbose statusCode 404
6.395 npm verbose pkgid rightpad@https://repository.example.com/rightpad/-/rightpad-1.0.1.tgz
6.395 npm error code E404
6.395 npm error 404 Not Found - GET https://repository.example.com/rightpad/-/rightpad-1.0.1.tgz
6.395 npm error 404
6.395 npm error 404  'rightpad@https://repository.example.com/rightpad/-/rightpad-1.0.1.tgz' is not in this registry.
6.395 npm error 404
6.395 npm error 404 Note that you can also install from a
6.395 npm error 404 tarball, folder, http url, or git url.
6.395 npm silly unfinished npm timer reify 1744266795483
6.395 npm silly unfinished npm timer reify:unpack 1744266795503
6.395 npm silly unfinished npm timer reifyNode:node_modules/rightpad 1744266795503
6.395 npm verbose cwd /
6.396 npm verbose os Linux 5.15.167.4-microsoft-standard-WSL2
6.396 npm verbose node v22.14.0
6.396 npm verbose npm  v11.3.0
6.396 npm verbose exit 1
6.396 npm verbose code 1
6.396 npm error A complete log of this run can be found in: /root/.npm/_logs/2025-04-10T06_33_14_780Z-debug-0.log
------
Dockerfile:9
--------------------
   7 |     RUN npm install -g npm@11.3.0
   8 |     COPY package*.json .
   9 | >>> RUN npm install --loglevel silly
  10 |     
--------------------
ERROR: failed to solve: process "/bin/sh -c npm install --loglevel silly" did not complete successfully: exit code: 1

[max-allan-cgr]

I am running Nexus3:

mkdir nexus-data
docker run -d -p 8081:8081 --name nexus -v`pwd`/nexus-data:/nexus-data -e NEXUS_CONTEXT=long/path sonatype/nexus3

And nginx:

cat > nginx.conf <<EOF
server {
        listen 8443 ssl;
        listen [::]:8443 ssl;
        server_name host.docker.internal;
        ssl_certificate          /etc/cert/server.crt;
        ssl_certificate_key      /etc/cert/server.key;
        location / {
               proxy_pass         http://host.docker.internal:8081/;
               proxy_redirect        off;
               proxy_set_header      Host $host;
               proxy_set_header      X-Real-IP $remote_addr;
               proxy_set_header      X-Forwarded-For $proxy_add_x_forwarded_for;
               proxy_set_header      X-Forwarded-Host $server_name;
               proxy_set_header      X-Forwarded-Proto $scheme;
               proxy_set_header      X-Forwarded-Port 8443;
       }
}
EOF
openssl req -new -newkey rsa:2048 -days 365 -nodes -x509 -keyout server.key -out server.crt --subj "/CN=host.docker.internal/"
docker run -d --rm --name nginx -v `pwd`:/etc/cert -v `pwd`/nginx.conf:/etc/nginx/conf.d/nginx.conf -p8443:8443 chainguard/nginx:latest-dev

Use nexus-data/admin-password file for the admin password to login to https://localhost:8443/long/path/ (accept the bad cert)
Create an "npm cache" repo with source as the upstream npmjs (optionally create a user, mine is "max" with password "max")

Then build your Dockerfile but with a real repo instead of example.com (optional auth line commented out, but it makes little difference either way):

FROM container-registry.oracle.com/os/oraclelinux:8-slim
RUN microdnf install npm nodejs gzip
RUN npm config set registry https://host.docker.internal:8443/long/path/repository/internal/
# RUN npm config set //host.docker.internal:8443/long/path/repository/internal/:_auth="$(echo -n 'max:max' | base64)" 
RUN npm config set strict-ssl false
RUN npm install -g n
RUN n stable
RUN npm install -g npm@11.3.0
COPY <<EOF package.json
{
  "name": "foo",
  "version": "1.0.0",
  "main": "index.js",
  "scripts": {},
  "author": "",
  "license": "MIT",
  "description": "",
  "dependencies": {
    "rightpad": "^1.0.1"
  }
}
EOF
RUN npm install --no-audit --loglevel silly

To build:

docker build --progress=plain --no-cache .
....skipping....
#13 [9/9] RUN npm install --no-audit --loglevel silly
#13 0.226 npm verbose cli /usr/local/bin/node /usr/local/bin/npm
#13 0.226 npm info using npm@11.3.0
#13 0.226 npm info using node@v22.14.0
#13 0.226 npm silly config load:file:/usr/local/lib/node_modules/npm/npmrc
#13 0.226 npm silly config load:file:/.npmrc
#13 0.226 npm silly config load:file:/root/.npmrc
#13 0.226 npm silly config load:file:/usr/local/etc/npmrc
#13 0.228 npm verbose title npm install
#13 0.228 npm verbose argv "install" "--no-audit" "--loglevel" "silly"
#13 0.228 npm verbose logfile logs-max:10 dir:/root/.npm/_logs/2025-04-10T10_01_54_735Z-
#13 0.231 npm verbose logfile /root/.npm/_logs/2025-04-10T10_01_54_735Z-debug-0.log
#13 0.439 npm silly logfile done cleaning log files
#13 0.466 npm silly packumentCache heap:4345298944 maxSize:1086324736 maxEntrySize:543162368
#13 0.478 npm silly idealTree buildDeps
#13 0.480 npm silly fetch manifest rightpad@^1.0.1
#13 0.480 npm silly packumentCache full:https://host.docker.internal:8443/long/path/repository/internal/rightpad cache-miss
#13 0.515 npm http fetch GET 200 https://host.docker.internal:8443/long/path/repository/internal/rightpad 35ms (cache miss)
#13 0.515 npm silly packumentCache full:https://host.docker.internal:8443/long/path/repository/internal/rightpad set size:undefined disposed:false
#13 0.518 npm silly placeDep ROOT rightpad@1.0.1 OK for: foo@1.0.0 want: ^1.0.1
#13 0.521 npm silly reify moves {}
#13 0.528 npm http cache rightpad@https://host.docker.internal:8443/long/path/repository/internal/rightpad/-/rightpad-1.0.1.tgz 1ms (cache hit)
#13 0.530 npm silly tarball no local data for rightpad@https://host.docker.internal:8443/long/path/repository/internal/rightpad/-/rightpad-1.0.1.tgz. Extracting by manifest.
#13 0.551 npm http fetch GET 200 https://host.docker.internal:8443/long/path/repository/internal/rightpad/-/rightpad-1.0.1.tgz 21ms (cache miss)
#13 0.560 npm silly ADD node_modules/rightpad
#13 0.561 
#13 0.561 added 1 package in 356ms
#13 0.561 npm verbose cwd /
#13 0.561 npm verbose os Linux 6.10.14-linuxkit
#13 0.561 npm verbose node v22.14.0
#13 0.561 npm verbose npm  v11.3.0
#13 0.561 npm verbose exit 0
#13 0.561 npm info ok
#13 DONE 0.6s

Can you try with --no-audit to remove all the failure messages because of auditing which is probably masking the problem in the logs.

And can you try with your own local Nexus repo, to rule out any weirdness on your local network like cache/proxy setup.

[max-allan-cgr]

Aha! I think @jamonation is right and it's something to do with the "resolved" replacement.

If I add a package-lock.json to my Dockerfile:

COPY <<EOF package-lock.json
{
  "name": "foo",
  "version": "1.0.0",
  "lockfileVersion": 3,
  "requires": true,
  "packages": {
    "": {
      "name": "foo",
      "version": "1.0.0",
      "license": "MIT",
      "dependencies": {
        "rightpad": "^1.0.1"
      }
    },
    "node_modules/rightpad": {
      "version": "1.0.1",
      "resolved": "https://registry.npmjs.org/rightpad/-/rightpad-1.0.1.tgz",
      "integrity": "sha512-WbDmWv4Sd54cqnpORqA8nW2x5Vag5iv7ODProdPN5yG6IOUSjheumUPfE/hY4IzQlijaE0TWSake12dTAZnR8w==",
      "license": "MIT"
    }
  }
}
EOF

THEN I get a 404 error and failures.

#16 0.201 npm verbose logfile /root/.npm/_logs/2025-04-10T11_19_14_362Z-debug-0.log
#16 0.377 npm silly logfile done cleaning log files
#16 0.401 npm silly packumentCache heap:4345298944 maxSize:1086324736 maxEntrySize:543162368
#16 0.408 npm silly idealTree buildDeps
#16 0.411 npm silly reify moves {}
#16 0.413 npm http cache rightpad@https://host.docker.internal:8443/rightpad/-/rightpad-1.0.1.tgz 0ms (cache hit)
#16 0.415 npm silly tarball no local data for rightpad@https://host.docker.internal:8443/rightpad/-/rightpad-1.0.1.tgz. Extracting by manifest.
#16 0.430 npm http fetch GET 404 https://host.docker.internal:8443/rightpad/-/rightpad-1.0.1.tgz 15ms (cache skip)
#16 0.433 npm verbose stack HttpErrorGeneral: 404 Not Found - GET https://host.docker.internal:8443/rightpad/-/rightpad-1.0.1.tgz
#16 0.433 npm verbose stack     at /usr/local/lib/node_modules/npm/node_modules/npm-registry-fetch/lib/check-response.js:103:15
#16 0.433 npm verbose stack     at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
#16 0.433 npm verbose statusCode 404
#16 0.433 npm verbose pkgid rightpad@https://host.docker.internal:8443/rightpad/-/rightpad-1.0.1.tgz
#16 0.433 npm error code E404
#16 0.433 npm error 404 Not Found - GET https://host.docker.internal:8443/rightpad/-/rightpad-1.0.1.tgz
#16 0.433 npm error 404
#16 0.433 npm error 404  'rightpad@https://host.docker.internal:8443/rightpad/-/rightpad-1.0.1.tgz' is not in this registry.
#16 0.433 npm error 404
#16 0.433 npm error 404 Note that you can also install from a
#16 0.433 npm error 404 tarball, folder, http url, or git url.
#16 0.433 npm silly unfinished npm timer reify 1744283954584

Using npm 11.2 works with that package-lock.json.
Or using 11.3.0 I can make it work if I replace the path in the package-lock.json with:

      "resolved": "https://registry.npmjs.org/long/path/repository/internal/rightpad/-/rightpad-1.0.1.tgz",

If I remove package-lock.json and rerun npm i then I get a new package-lock.json with that path in the "resolved".

Hopefully this is enough info for someone to fix it!