Issue while installing npm packages
See original GitHub issuewhy I am getting this error?
node v16.15.1 npm v8.11.0
“nx”: “14.3.1”,
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: jasmine-marbles@0.8.4
npm WARN Found: rxjs@7.4.0
npm WARN node_modules/rxjs
npm WARN peer rxjs@"^6.5.3 || ^7.4.0" from @angular/common@14.0.1
npm WARN node_modules/@angular/common
npm WARN peer @angular/common@"14.0.1" from @angular/forms@14.0.1
npm WARN node_modules/@angular/forms
npm WARN 4 more (@angular/platform-browser, ...)
npm WARN 6 more (@angular/core, @angular/forms, @angular/router, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer rxjs@"^6.5.3" from jasmine-marbles@0.8.4
npm WARN node_modules/jasmine-marbles
npm WARN jasmine-marbles@"~0.8.4" from @nrwl/angular@14.3.1
npm WARN node_modules/@nrwl/angular
npm WARN
npm WARN Conflicting peer dependency: rxjs@6.6.7
npm WARN node_modules/rxjs
npm WARN peer rxjs@"^6.5.3" from jasmine-marbles@0.8.4
npm WARN node_modules/jasmine-marbles
npm WARN jasmine-marbles@"~0.8.4" from @nrwl/angular@14.3.1
npm WARN node_modules/@nrwl/angular
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: rxjs-for-await@0.0.2
npm WARN Found: rxjs@7.4.0
npm WARN node_modules/rxjs
npm WARN peer rxjs@"^6.5.3 || ^7.4.0" from @angular/common@14.0.1
npm WARN node_modules/@angular/common
npm WARN peer @angular/common@"14.0.1" from @angular/forms@14.0.1
npm WARN node_modules/@angular/forms
npm WARN 4 more (@angular/platform-browser, ...)
npm WARN 6 more (@angular/core, @angular/forms, @angular/router, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer rxjs@"^6.0.0" from rxjs-for-await@0.0.2
npm WARN node_modules/rxjs-for-await
npm WARN rxjs-for-await@"0.0.2" from @nrwl/angular@14.3.1
npm WARN node_modules/@nrwl/angular
npm WARN 1 more (@nrwl/node)
npm WARN
npm WARN Conflicting peer dependency: rxjs@6.6.7
npm WARN node_modules/rxjs
npm WARN peer rxjs@"^6.0.0" from rxjs-for-await@0.0.2
npm WARN node_modules/rxjs-for-await
npm WARN rxjs-for-await@"0.0.2" from @nrwl/angular@14.3.1
npm WARN node_modules/@nrwl/angular
npm WARN 1 more (@nrwl/node)
Issue Analytics
- State:
- Created a year ago
- Reactions:4
- Comments:5
Top Results From Across the Web
npm install error from the terminal - Stack Overflow
Running just "npm install" will look for dependencies listed in your package.json. The error you're getting says that you don't have a ...
Read more >Common errors | npm Docs
Possible temporary npm registry glitch, or corrupted local server cache. Run npm cache clean and/or try again later. · This can be caused...
Read more >How to solve npm ERR! code 1 when running npm install
Fix npm error code 1 by updating your dependencies · Update one package version in package.json file · Then run npm install ·...
Read more >NPM install error - Material Design for Bootstrap
i am facing the below problem while installing node modoule Can someone tell me ... /Users/robwheeler/CodeProjects/CollegeRecruiter/imports/package.json npm ...
Read more >cannot find module [Node npm Error Solved] - freeCodeCamp
How to Fix the "cannot find module" Error · delete the node modules folder by running rm -rf node_modules · delete package.lock.json file...
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
I had the same issue after migrating nx 14.4.0 to 14.4.2. I updated jasmine-marbles to ~0.9.2 in package.json after deleting package-lock.json and reinstalled node_modules…
=> No issue with npm install anymore
It seems like the old dependency is just not correctly removed/updated…
Found a related issue where it is discussed: https://github.com/nrwl/nx/issues/10308