-
Notifications
You must be signed in to change notification settings - Fork 4k
Closed
Labels
Bugthing that needs fixingthing that needs fixingPriority 1high priority issuehigh priority issueRelease 7.xwork is associated with a specific npm 7 releasework is associated with a specific npm 7 release
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
On Node 10, Node 12 and Node 14 with npm 6.x or npm 7.5.2, the installation step (npm ci) works fine.
On Node 16.6.1 with npm 7.20.3, installation fails as follows:
https://github.com/qunitjs/qunit/runs/3271660304
pm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
... 2.16.0: building release
npm WARN old lockfile This is a one-time fix-up, please be patient...
... 2.15.0: installing development dependencies from npm
npm WARN old lockfile
npm WARN old lockfile HttpErrorGeneral: 404 Not Found - GET https://registry.npmjs.org/npm-reporter - Not found
npm WARN old lockfile at /opt/hostedtoolcache/node/16.6.1/x64/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:95:15
npm WARN old lockfile at runMicrotasks (<anonymous>)
npm WARN old lockfile at processTicksAndRejections (node:internal/process/task_queues:96:5)
npm WARN old lockfile at async Array.<anonymous> (/opt/hostedtoolcache/node/16.6.1/x64/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:681:9)
npm WARN old lockfile Could not fetch metadata for npm-reporter@1.0.0 HttpErrorGeneral: 404 Not Found - GET https://registry.npmjs.org/npm-reporter - Not found
npm WARN old lockfile at /opt/hostedtoolcache/node/16.6.1/x64/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:95:15
npm WARN old lockfile at runMicrotasks (<anonymous>)
npm WARN old lockfile at processTicksAndRejections (node:internal/process/task_queues:96:5)
npm WARN old lockfile at async Array.<anonymous> (/opt/hostedtoolcache/node/16.6.1/x64/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:681:9) {
npm WARN old lockfile headers: [Object: null prototype] {
npm WARN old lockfile date: [ 'Sun, 08 Aug 2021 01:40:59 GMT' ],
npm WARN old lockfile 'content-type': [ 'application/json' ],
npm WARN old lockfile 'content-length': [ '21' ],
npm WARN old lockfile connection: [ 'keep-alive' ],
npm WARN old lockfile 'cf-ray': [ '67b50a2f78865ec6-IAD' ],
npm WARN old lockfile vary: [ 'Accept-Encoding' ],
npm WARN old lockfile 'cf-cache-status': [ 'MISS' ],
npm WARN old lockfile 'expect-ct': [
npm WARN old lockfile 'max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"'
npm WARN old lockfile ],
npm WARN old lockfile server: [ 'cloudflare' ],
npm WARN old lockfile 'x-fetch-attempts': [ '1' ],
npm WARN old lockfile 'x-local-cache-status': [ 'skip' ]
npm WARN old lockfile },
npm WARN old lockfile statusCode: 404,
npm WARN old lockfile code: 'E404',
npm WARN old lockfile method: 'GET',
npm WARN old lockfile uri: 'https://registry.npmjs.org/npm-reporter',
npm WARN old lockfile body: { error: 'Not found' },
npm WARN old lockfile pkgid: 'npm-reporter@1.0.0'
npm WARN old lockfile }
Expected Behavior
No failure, as it was on Node 14 with npm 7.5.2.
Steps To Reproduce
Environment
- OS: Ubuntu 20.04
- Node: 16.6.1
- npm: 7.20.3
Metadata
Metadata
Assignees
Labels
Bugthing that needs fixingthing that needs fixingPriority 1high priority issuehigh priority issueRelease 7.xwork is associated with a specific npm 7 releasework is associated with a specific npm 7 release