Repository navigation
[BUG] unsupported engine warning only displays after initial install #4987
Description
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
❯ npm i npm@latest
added 1 package, and audited 202 packages in 2s
11 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
❯ npm ls node-gyp
npm-test@1.0.0 /Users/lukekarrys/Desktop/garbage/npm-test
└─┬ npm@8.12.0
├─┬ @npmcli/run-script@3.0.2
│ └── node-gyp@9.0.0 deduped
└── node-gyp@9.0.0
❯ npm i npm
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: 'node-gyp@9.0.0',
npm WARN EBADENGINE required: { node: '^12.22 || ^14.13 || >=16' },
npm WARN EBADENGINE current: { node: 'v12.13.0', npm: '8.12.0' }
npm WARN EBADENGINE }
up to date, audited 202 packages in 985ms
11 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
❯ npm ls node-gyp
npm-test@1.0.0 /Users/lukekarrys/Desktop/garbage/npm-test
└─┬ npm@8.12.0
├─┬ @npmcli/run-script@3.0.2
│ └── node-gyp@9.0.0 deduped
└── node-gyp@9.0.0
❯ npm i npm
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: 'node-gyp@9.0.0',
npm WARN EBADENGINE required: { node: '^12.22 || ^14.13 || >=16' },
npm WARN EBADENGINE current: { node: 'v12.13.0', npm: '8.12.0' }
npm WARN EBADENGINE }
up to date, audited 202 packages in 934ms
11 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
Expected Behavior
I expect to see the unsupported engines warning on the initial install.
Activity