-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broken npm ci since forks replaced official dependencies #5929
Comments
We're looking into this! In general, we recommend that folks depend upon a prebuilt bundle like |
Thank you @nicolaskruchten 🙂 |
@aubm are you able to use |
@archmoj just to be clear, that would mean not using npm, right? |
No, you can use NPM: https://www.npmjs.com/package/plotly.js-dist or https://www.npmjs.com/package/plotly.js-dist-min |
Oh perfect thank you 👌 that should do it |
No. You simply need to uninstall However if you have |
Noted, thank you 🙂 |
We are having the same issue when trying to build the package on a build/ci machine that doesn't have open access to the internet (e.g. github). I used |
Hello,
It appears that recent changes in
package.json
have broken thenpm ci
with npm < v7.xProbably due to changes to the lockfile.
Source: https://github.blog/2020-10-13-presenting-v7-0-0-of-the-npm-cli/
Steps to reproduce the error with npm 6
npm ci
exists with the following error:Looking in
package-lock.json
to see the details aboutzero-crossings
, I can see theresolved
field is ignored.We should probably find a workaround this if we want to keep supporting npm < 7.
The text was updated successfully, but these errors were encountered: