Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
npx npm-force-resolutions failed
See original GitHub issue15:46:43 npm ERR! code ELIFECYCLE
15:46:43 npm ERR! errno 1
15:46:43 npm ERR! i18n@0.13.0 preinstall: npx npm-force-resolutions
15:46:43 npm ERR! Exit status 1
15:46:43 npm ERR!
15:46:43 npm ERR! Failed at the i18n@0.13.0 preinstall script.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
npm-force-resolutions not working when installing a new ...
The best solution for me to automate this was modifying preinstall script as above: "preinstall": "npm install --package-lock-only ...
Read more >Npm install fails in npm-force-resolutions if there is a space in ...
npx force -resolutions does not run when no package-lock.json is detected, and allows the next command inline to be executed as normal. This...
Read more >npm-force-resolutions
NPM Force Resolutions. This packages modifies package-lock.json to force the installation of specific version of a transitive dependency ...
Read more >Wes Bos on Twitter: "I'm dumb! npm-force-resolutions does ...
with npm, how do I force a version of a nested dependency? npm-force-resolutions doesn't do nested dependencies. Is there some command I can...
Read more >NPM How to pin dependency version of a dependency
npm -force-resolutions offers a simple solution. We just need to add preinstall and resolutions into a package.json file. "scripts": { " ...
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 Free
Top 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
It is now running without errors. Thanks for the quick fix.
hotfix published as i18n@0.13.1 (https://github.com/mashpie/i18n-node/releases/tag/0.13.1)
@amlrJan2015, would you mind to retry?