at some point I got an error after each npm install. Says something about gyp error but I have no idea how to fix it. That package was working with the old node version. I've tried to remove manually node and install it again but doesn't seem to work (or maybe I'm not doing it properly...)
Log:
https://pastebin.com/crzWVwJn
Parcel was the problem. I'm not going to use it anymore so I removed it. But first I've tried to update to last version and same problem with the lmdb-store dependency.
Related
Getting this weird error while installing expo-modules-core. I have clean the npm cache but it keeps giving me Not Found - GET https://registry.npmjs.org/react-navigation-reanimated - Not found 404 error. Although I'm not installing it.
My package.json file mistakenly contains this wrong package name i.e. react-navigation-reanimated, its react-native-reanimated actually. Removing that from the package.json removed the error.
I am trying to get rid of the following error message.
patch-package 6.2.2
Applying patches...
Error: Patch file found for package mongodb-query-parser which is not present at node_modules/mongodb-query-parser
This message appears when I try to install mongo-express. Locally this is no problem, because npm install keeps progressing after the error message.
But when I try to run it on gitlab-pipeline it exits the job.
Is there any workaround?
Temporary quick fix is to install mongo-express without the postinstall.
npm install mongo-express --ignore-scripts && npm install
That way the patch-package isn't called and at least the CI doesn't break. But I'm not sure how unsecure this is...
Hopefully going to be fix soon! I opened an issue
Cheers
I am struggling to understand why trying to run a npm install fails when one of the packages in the list is deprecated. A warning shouldn't make the command fail, shouldn't it?
I found the culprit PR. They created a version that hard breaks..
https://github.com/aspnet/SignalR/pull/2057
Got to love MS..
I will try to give as much information as possible on my problem, however part of the problem is that it prevents me from seeing everything that went wrong.
First of all, when I installed generator-gulp-bootstrap, it gave me a bunch of peer dependency warnings, but yeoman itself appeared to install fine, and they were just warnings, not actual errors.
Then, when i try to start a new bootstrap project in yeoman yo gulp-bootstrap it downloads a ridiculous amount of files (88.5mb)-- which is where I became concerned because no npm install has ever taken this long or downloaded this many files. I kept seeing warnings pop up as it was scrolling by, they looked like deprecation warnings, but they flew by too fast to be sure. I figured I would just go back and double check on them when it was finished, but that's when I noticed my biggest problem -- it doesn't let me scroll up very far. It doesn't even scroll past the top of the file structure map that it shows when a package is done installing. So from there I went to the npm-debug.log to try and find what went wrong, but I noticed it's 12,363 lines long -- and I have no idea where to look, and I don't know if I can even post that many characters in a post here.
I only really have 1 thing to go off - the one visible error at the bottom of the install, it won't let me scroll up far enough in my terminal to see what else went wrong, and I have no idea where to look in the debug log. I don't think I should post the debug log here because its 12.3k lines long....anyone have any idea what I should do from here? Thanks. I have tried removing all yeoman components and completely reinstalling yeoman, as well as the generators, and also reinstalled node-sass. Not sure what else to do now.
58576 error Windows_NT 6.1.7601
58577 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Elliot\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install"
58578 error node v4.1.1
58579 error npm v3.3.5
58580 error code ELIFECYCLE
58581 error node-sass#0.9.6 install: `node build.js`
58581 error Exit status 1
58582 error Failed at the node-sass#0.9.6 install script 'node build.js'.
58582 error This is most likely a problem with the node-sass package,
58582 error not with npm itself.
58582 error Tell the author that this fails on your system:
58582 error node build.js
58582 error You can get their info via:
58582 error npm owner ls node-sass
58582 error There is likely additional logging output above.
You should open a bug report:
Failed at the node-sass#0.9.6 install script 'node build.js'.
This is most likely a problem with the node-sass package
It might be that you don't have a compatible C compiler on your machine, or maybe the node-sass build is broken for windows.
In the meantime, just try the usual debugging npm installation issue:
At this point I'd make sure npm and node are on the latest version.
Then I'd try to only run npm install node-sass.
When I do npm list --global, one package, phonegap, shows as invalid.
npm ERR! invalid: phonegap#5.0.0-0.28.1 /usr/local/lib/node_modules/phonegap
No other packages have any errors or problems. I’ve tried to look into this, and learned that the message means a dependency is unfulfilled, but I can’t figure out which one. If I run npm update --global phonegap it exits cleanly, with no errors.
I originally installed npm & node via Homebrew, if that’s relevant. Here’s my full list of globally installed packages.
How do I diagnose this?
Have you tried changing the permissions for that package? I recently had a similar problem with global packages and it turned out to be a permissions issue
https://docs.npmjs.com/getting-started/fixing-npm-permissions