-
Notifications
You must be signed in to change notification settings - Fork 146
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
grunt-browserify isn't compatible with Node.js v12 #410
Comments
There's an open issue and PR for watchify to update over at browserify/watchify#374 |
I can install It seems that support for Node 12 was backported to fsevents 1.x in this commit and released as
I would wager that |
@DirtyHairy hm, I'm still seeing the error in the logs, this is a fresh install, no node_modules folder after
|
Ah-ha, got it: according to this comment |
aha! It appears that the directory I'd been testing in had a
|
This is because in its dependency chain is a version of fsevents that isn't compatible with Node.js v12, and it won't be made compatible.
The full chain is
watchify@^3.6.1 -> chokidar@1.7.0 -> fsevents@1.2.4
And it results in a nasty and confusing install time error that looks like something went horribly wrong (because, yay, native modules). You can see an example of said error here: openpgpjs/openpgpjs#1054
I also note that this project hasn't received any updates since May 3, 2018; Are any further updates planned or is this project at end-of-life and should be marked as deprecated in the npm registry?
The text was updated successfully, but these errors were encountered: