Node 10: Lots of warnings and errors upon install #229
Comments
Merged
|
Facing the same issue Node 10.7 too |
|
Same issue. Same Node version (10.7.0). On Mac High Sierra. I seem to have fixed this by uninstalling and reinstalling npm. I used the "More Severe Uninstalling" section of this guide. |
|
I face this issue too..... |
|
xcode->product->clean |
|
Sadly, @elarbee's suggestion did not work for me (on MacOS High Sierra with Node 10.7). I have also tried running |
|
fixed by using older node version (LTS): |
|
In my case the errors were only caused by I'd recommend anyone else running into this issue run |
|
Thanks for the tip about the version number, @JakeSidSmith! Because we use yarn in our project, we were able to solve this without explicitly upgrading any dependencies: We used ... and updated the resolutions in our {
"resolutions": {
"jest/jest-cli/jest-haste-map/sane": "1.2.4",
"webpack/watchpack/chokidar/fsevents": "1.2.4"
}
} |
|
@Vages Thanks for the tip! Although I had to add |
|
In my case, it was because only required So @Vages, you might be able to avoid having to specify resolutions. |
|
Hehe, yeah. I'd be comfortable doing that in a hobby project, but after some experiments in my early days of using |
|
Faced same issue, following @rwendell's comment, downgraded to node version 8.11.3 and everything started working normally. |
|
Is this stil an issue? |
|
@pipobscure it is not an issue in |
|
I found out that the node_modules directory was installed as a different user and group on my Mac. I just ran a CHOWN command to make it match the rest of the files in my directory:
And the rest of the install worked like a charm. Actually, it errored out again when running as sudo, but running it WITHOUT sudo worked great. Also, you can always try running the (for the record, I got the issue when it came to install |
|
You should never install using sudo. You’re creating potential security holes doing that. But if I understand you correctly, when just installing without sudo everything is fine? |
|
After setting the proper owner for the directory it worked fine for me. But that was my issue relating to Honestly, I don't know what will fix it for you, but the above list gives you some options to try. |
|
LoL @byusyephen I’m the author and was just trying to make sure you figured it out and there wasn’t an actual current issue that i’d need to fix😀 |
|
Glad you are checking in. It's a good sign that you are accountable and proactive. |
|
I'm still experiencing this issue. The only thing that "works" is reverting back to node v8. However, I'd like to take advantage of the improved async stack traces that node v12 offers. Here's my stack trace on running npm install: |
|
Hi, your problem is entirely different. Here are things to try:
You can install the newest version of either v1.2.x or 2.x you just have to make sure you actually get the newest one. If you are working with a new node version/release (such as you are with 12.4.0) there will never be prebuilt binaries. So you’ll have to then wait at least 1 month until the people maintaining this package have had a chance to release new binaries for v1.2.x. for v2.x new binaries are never needed. So if you can update, that will eliminate your problem. |
|
I ran into this problem and found that it was caused by webpack not finding the configuration file ERROR in ./node_modules/_fsevents@1.2.9@fsevents/node_modules/tar/lib/unpack.js ERROR in ./node_modules/_fsevents@1.2.9@fsevents/node_modules/tar/lib/pack.js ERROR in ./node_modules/_fsevents@1.2.9@fsevents/node_modules/tar/lib/mkdir.js ERROR in ./node_modules/_fsevents@1.2.9@fsevents/node_modules/tar/lib/list.js I executed the following code to solve the problem
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Getting a bunch of warnings and errors when installing my dependencies with node 10.
Possibly related to:
nodejs/node-gyp#942
kelektiv/node.bcrypt.js#634
Node:
10.5.0NPM:
6.1.0/6.2.0NVM:
0.33.1/0.33.11npm list fsevents:Errors during
npm install:The text was updated successfully, but these errors were encountered: