fsevents is dealt differently in mac and other linux system. Linux system ignores fsevents whereas mac install it. As the above error message states that fsevents is optional and it is skipped in installation process. You can run npm install –no-optional command in linux system to avoid above warning. Further information https://github.com/npm/npm/issues/14185 https://github.com/npm/npm/issues/5095
Things to try: make sure you have internet connection: ping 8.8.8.8 make sure you have DNS resolver working: ping www.google.com make sure you can access registry.npmjs.org: ping registry.npmjs.org make sure you can connect via https. Try in your browser: https://registry.npmjs.org/ Make sure you are trying to connect to: registry.npmjs.org and not to: “registry.npmjs.org registry.npmjs.org:443” or … Read more
In the new version of npm (v7), by default, npm install will fail when it encounters conflicting peerDependencies. It was not like that before. Take a look here for more info about peer dependencies in npm v7. The differences between the two are below – –legacy-peer-deps: ignore all peerDependencies when installing, in the style of … Read more
Doing a symlink solves the issue: ln -s /usr/bin/nodejs /usr/bin/node (My thanks and +1 vote to bodokaiser’s answer).
npm no longer installs peer dependencies so you need to install them manually, just do an npm install on the needed deps, and then try to install the main one again. Reply to comment: it’s right in that message, it says which deps you’re missing UNMET PEER DEPENDENCY angular-animate@^1.5.0 +– UNMET PEER DEPENDENCY angular-aria@^1.5.0 +– … Read more
From the npm docs: In short, the main differences between using npm install and npm ci are: The project must have an existing package-lock.json or npm-shrinkwrap.json. If dependencies in the package lock do not match those in package.json, npm ci will exit with an error, instead of updating the package lock. npm ci can only … Read more
TL;DR: You may be arriving upon this answer if you’re upgrading from NPM v6 / Node v12. NPM v7+ installs peerDependencies by default; this is not the case with previous versions of NPM. NPM modules must name specific versions of their peerDependencies If you already have a peerDependency installed, but not with a version named … Read more
Update 3: As other answers point out as well, the npm ci command got introduced in npm 5.7.0 as additional way to achieve fast and reproducible builds in the CI context. See the documentation and npm blog for further information. Update 2: The issue to update and clarify the documentation is GitHub issue #18103. Update … Read more
you just provide one <folder> argument to npm install, argument should point toward the local folder instead of the package name: npm install /path
Running this command was my mistake. npm config set prefix /usr/local Path /usr/local is not for windows. This command changed the prefix variable at ‘C:\Program Files (x86)\Git\local’ To access and make a change to this directory I need to run my cmd as administrator. So I did: Run cmd as administrator Run npm config edit … Read more