Error when regenerating npm-shrinkwrap
See original GitHub issueI noticed that update-internal-deps
command is failing when regenerating npm-shrinkwrap.json
.
It throws this error:
npm ERR! Problems were encountered
npm ERR! Please correct and try again.
npm ERR! peer invalid: acorn@^6.0.0, required by acorn-dynamic-import@4.0.0
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>
It can be fixed by installing acorn@^6.0.0
with npm i acorn@6.0.0 --save
, but it adds acorn dependency as a first level dependency, which is not what we want (afaik).
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
npm related tasks are throwing errors during installations
First of all you need to make sure that your node and npm versions are up to ... Force clean the entire NPM...
Read more >npm shrinkwrap error - Popular Blocks
Description. npm install fails after generating a npm-shrinkwrap.json file. npm versions. 2.15.11 works; 3.10.10 fails; 4.1.2 fails ...
Read more >Fix to The “npm ERR! Object for dependency @Babel ...
Fix to The “npm ERR! Object for dependency @Babel/generator is empty” Error ... “If using a shrinkwrap, regenerate with npm shrinkwrap.”.
Read more >npm-shrinkwrap
This command repurposes package-lock.json into a publishable npm-shrinkwrap.json or simply creates a new one. The file created and updated by this command ...
Read more >[SOLVED] Fix npm ERR! code EINTEGRITY, integrity ...
Clean npm cache, node_modules, package-lock.json files to recover from all 'npm ERR! code EINTEGRITY' error messages during 'npm install'
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry, I didn’t label this issue 🤦♂️
It’s meant for Frontend, it is relatively important when it comes to development because we cannot update CARTO.js version in Builder until we fix this, for example.
But it’s better to ask @rjimenezda and assign the proper priority under RT 😃
Closed via #14369