Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork1.9k
Closed
Milestone
Description
Hello,
It appears that recent changes inpackage.json have broken thenpm ci with npm < v7.x
Probably due tochanges to the lockfile.
Prior to npm 7 yarn.lock files were ignored
Source:https://github.blog/2020-10-13-presenting-v7-0-0-of-the-npm-cli/
Steps to reproduce the error with npm 6
cat '{ "name": "test-project", "version": "1.0.0", "description": "", "main": "index.js", "scripts": { "test": "echo \"Error: no test specified\" && exit 1" }, "author": "", "license": "ISC", "dependencies": { "plotly.js": "^2.5.0" }}' > package.jsonnpm install --package-lock-onlynpm cinpm ci exists with the following error:
npm ERR! code ETARGETnpm ERR! notarget No matching version found for zero-crossings@1.1.0.npm ERR! notarget In most cases you or one of your dependencies are requestingnpm ERR! notarget a package version that doesn't exist.npm ERR! A complete log of this run can be found in:npm ERR! /Users/aurelienbaumann/.npm/_logs/2021-09-07T20_14_08_058Z-debug.logLooking inpackage-lock.json to see the details aboutzero-crossings, I can see theresolved field is ignored.
"zero-crossings": { "version": "1.1.0", "resolved": "git+https://github.com/plotly/zero-crossings.git#4746771f490344e21c84d1f631cb661d8c5ff508"}We should probably find a workaround this if we want to keep supporting npm < 7.
Metadata
Metadata
Assignees
Labels
No labels