Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Native crash in Node 10 #2162
I installed Node 10 on MacOS and Win 10. Used it for various node things with no issues. But starting gulp always results in a native crash. Smells like a Node bug but I report it here because I haven't seen it anywhere else.
Same steps for Mac or Win...
Same result if I run
What version of gulp are you using?
$ gulp -v
If you can't reproduce this, I'm happy to debug more, but since I see it in 2 different environments, hopefully it's easy to reproduce.
referenced this issue
Apr 25, 2018
I tried the following configurations (using Linux):
I am unable to reproduce your issue (see last line). The only difference is that I am using Linux instead of Mac or Windows.
Could you try to use Gulp 4.0.0 on your system and report if the error still happens? It would at least provide a mitigation for the issue.
The next step would be to locate the line actually causing the error: the Node dump is not very helpful unfortunately.
I'm facing the same issue using Windows 10 and Node 10.
Just another note that we've started experiencing this on a daily Travis cron, using Gulp 3.9.1, that had been working fine until yesterday - with no changes for months.
Given that Gulp 4 isn't ready for prime time yet, it would be nice to see a fix backported to Gulp 3. I'm not sure exactly what's involved but it's possible it's just a dependency update. But I am assuming the best solution for now is just not to use Node 10!
@phated Got it - thank you! I did indeed get confused.
For others coming across this, here's what you need to do for Node 10 support (if using Yarn):
If using npm with a package-lock.json the process will probably be fairly similar.
(Be careful modifying your lock file. There's probably a better way to do it!)
Same issue with the console output.