-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
With Node 6, Gulp outputs more JS stack traces than useful messages #1628
Comments
BTW, this is how you downgrade to Node 5 in homebrew:
|
FWIW, I no longer see the long stack traces with gulp, just a warning:
and the rest of the output is normal so this doesn't seem so severe now. Maybe sth changed in the logging level? Could you remove |
It's actually the same issue. Even when deleting the package folder and reinstalling everything. It seems to be related to the old version of "graceful-fs" If I do a "npm ls graceful-fs" - as suggested in the debug output - I see the following in my project:
The only old version < 4 is used by the "glob" package. Maybe this can be fixed - as it's pretty darn old. Easiest upgrade would be possibly to update to a more recent version of "glob-watcher" which is currently at 3.0.0. |
@JohnAlbin I've looked at your gist and it's node-sass that generates those stack traces, not Gulp. Gulp only prints a small harmless warning and that won't be fixed in Gulp v3 according to #1571. The node-sass issue is sass/node-sass#1484, it's already fixed and the next node-sass version will contain the fix. So I think this issue should be closed as it's unrelated to Gulp. |
@mgol thanks for looking into this and giving a clear response! |
I tried out Node 6 and, after deleting node_modules and running
npm install
, when I rungulp
, I receive pages and pages of "JS stack trace"s. Starting with:Here's the full output: http://pastebin.com/6Zxgz8Ar
It makes it really, really difficult to use Gulp 3 on Node 6 if I have difficulty finding the normal output amongst the gobs of undesirable stack traces.
I'm fairly certain this is the fall out of #1571
I know that newer vinyl-fs versions don't use graceful-fs 3 or earlier, but we can't upgrade to that because it will cause API breakage.
One solution to this would be to update an older version vinyl-fs to not use graceful-fs 3 or earlier. And then to update gulp 3.9.x branch with the fixed dependencies.
Given the number of issues I see open for vinyl-fs, it doesn't look like Gulp 4 will be released quick enough to resolve this Node 6 issue in a timely matter (1-2 weeks from now.) Homebrew just upgraded me to Node 6 and the number of people who are upgrading is going to keep growing, so this is a critical issue, imo.
The text was updated successfully, but these errors were encountered: