Can't run npm install .
See original GitHub issueWhen I run npm install .
I get the following error.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: Livemarks@undefined
npm ERR! Found: prettier@2.2.1
npm ERR! node_modules/prettier
npm ERR! peer prettier@">=1.13.0" from eslint-plugin-prettier@3.3.1
npm ERR! node_modules/eslint-plugin-prettier
npm ERR! peer eslint-plugin-prettier@"^3.0.1" from eslint-plugin-mozilla@2.9.2
npm ERR! node_modules/eslint-plugin-mozilla
npm ERR! dev eslint-plugin-mozilla@"2.9.2" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer prettier@"^1.17.0" from eslint-plugin-mozilla@2.9.2
npm ERR! node_modules/eslint-plugin-mozilla
npm ERR! dev eslint-plugin-mozilla@"2.9.2" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /home/tom/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/tom/.npm/_logs/2021-01-24T15_43_08_092Z-debug.log
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Can't run npm install - node.js - Stack Overflow
sudo npm install npm WARN enoent ENOENT: no such file or directory, open '/var/www/html/mg/package.json' npm WARN mg No description npm WARN mg ...
Read more >5 Ways to Fix the Npm Install Not Working Issue
Way 1. Make Sure Npm Is Installed · Way 2. Make Sure There Is a Package.json File · Way 3. Delete Lock File...
Read more >How to fix npm install command not working
The error above happens when npm can't be found under the PATH environment variable. First, you need to make sure that npm is...
Read more >Problem with npm install - M220JS - MongoDB
Remove the node_modules folder inside the project folder where the package. · Run npm update -g npm · Execute this command by running...
Read more >Common errors | npm Docs
Some strange issues can be resolved by simply running npm cache clean and trying again. · If you are having trouble with npm...
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
Well, I cannot reproduce plus CI works fine. So, it’s something on your system that was triggered by the change.
Try using the latest Node.js 14.x after properly removing any other versions including npm. npm cache clean -fg might also help.
On Sun, Jan 24, 2021, 18:01 Tom Schuster notifications@github.com wrote:
Always stick to LTS 😃
On Sun, Jan 24, 2021, 18:16 Tom Schuster notifications@github.com wrote: