-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node: 12.2.0 throws error during npm install #278
Comments
Install fsevents@1.2.9 and it should work. |
it works for node 10.15.3 |
Anyone hitting issues with 1.2.9, remember to make sure you've updated node-sass ( |
This is fixed with fsevents@1.2.9 for the v1.x branch. |
1.2.9 seems to be still broken on node 12.1.0 :( |
Looking at that log, it’s clearly 1.2.4 and NOT 1.2.9 I assume there is something in a lockfile that prevents getting 1.2.9 |
@pipobscure You are right, my bad, I should have used |
Check your package-lock.json, it may contain dependency that requires fsevents at a low level like 1.1.0, which bothered me the whole day. |
the |
- add npm install node-sass as recommended on this post fsevents/fsevents#278 (comment)
I'm using version Build log
|
Deleting package-lock.json and npm i worked for me. |
I've tried all of the mentioned actions. It doesn't work. |
@Webbrother fsevents version? |
@paulmillr As I said before I've tried everything. I've tried to install fsevents@1.2.9. I've tried to delete package-lock.json. Doesn't work. |
As i've said: what is your fsevents version from package-lock.json? version 1 is unsupported. You need to always use v2. If you have v1 somewhere that'll cause the issue. |
@paulmillr I tried to install the latest version of fsevents, but it also didn't solve the problem.
Is it correct list of commands? UPD |
you should update these dependencies; if this doesn't help you should tell dependency maintainers to update chokidar or fsevents to latest versions. |
I'm facing this issue after I remove yarn.lock and reinstalling the problem seems to be solved. Environment: yarn.lock |
@suraneti read my comments |
…versions - specifically fsevents: fsevents/fsevents#278
Like @nassif7 said, the issue for me was More generally speaking, if you're not using react-scripts then find which package(s) you have that depend on fsevents and try updating them. |
For those using yarn, I added the following to my "resolutions": {
"fsevents": "1.2.9",
"**/fsevents": "1.2.9"
} |
Had this with Angular-CLI.. Removing package-lock.json fixed it. |
I use yarn instead of npm. |
Be aware that adding the Seems like best thing is to chase up your dependencies and create PRs for those using older versions of fsevents. |
I found out that I was using outdated version of react-scripts I installed the latest one using |
fsevents/fsevents#278 fsevents 1.2.9+ is required for proper macOS Catalina support. Without that, a yarn install fails. We had 1.2.7 installed. Yarn doesn't offer a good way to update a subdependency. yarnpkg/yarn#4986 (comment) This comment suggests deleting the package you want to upgrade from the yarn.lock file and running `yarn install`. So, that's exactly what I did. Now, fsevents installs without errors.
No brainer but, in addition to the above versioning solutions (which work mostly), my team updated the yarn.lock file and I started getting this fsevents build error. I tried all combinations of versions but the problem was the yarn was caching some versioning details and was not letting it go even when reinstalled. I had to restart my system and it started working. Just putting this out there since all the caching and threading done by Yarn for faster installations, over long periods introduces package resolution problems. The good old restart your machine worked for me. |
Hey folks, we must ask maintainers of software which uses fsevents to upgrade to fsevents 2, which doesn't have these problems. Please comment in issues mentioned in #325. |
solve using this code:
|
If I run yarn with the resolution in place, and then delete the resolution from the package.json, commiting just the yarn.lock, I get the best of both worlds. Does anyone know of a reason not to do this? Running |
Had this issue with fsevents@1.2.7, solved it by upgrading the package that was using fsevents (found via |
These steps worked for me |
Use Node: 12.2.0
Command:
npm install
Sorry for long error logs
The following issue occurs,
The text was updated successfully, but these errors were encountered: