My workflow is still not working, even though I removed the lingering gulp file that was present in the usr/local/bin path. I went onto the gulpjs repo on Github under issue #1571 from March 17, 2016 (yes, March 17) and it stated the following:
We are aware of the graceful-fs deprecation warning upon install of gulp 3.x.
This is due to:
1. our graceful-fs devDependency
2. the vinyl-fs dependency
Both of which we are unable to upgrade due to API breaking changes.
There is nothing wrong with the dependency, especially since it is only used in development. We will be updating or removing it in gulp 4 and the message will go away.
Please do not open issues about this topic.
-The gulp team
The issue had been immediately closed. I had kept on receiving that error every time I had done an npm install in a repo for months but thought nothing of it. No one else did until their workflows stopped working.
I was actually directed to that issue from another issue on the gulpjs repo:
With Node 6, Gulp outputs more JS stack traces than useful messages #1628:
I tried out Node 6 and, after deleting node_modules and running
npm install, when I run
gulp, I receive pages and pages of “JS stack trace”s. Starting with:
(node:94076) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
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.
And it just gets worse as you scroll further down the page. Gulp 4 was supposed to be already released by now, but it is not. That means if we want to have a nice workflow, we basically can’t use Gulp. We have to find a non-Gulp way of setting up our workflows. No way am I going back to Grunt, which I don’t even know if it is compatible either. My only recourse seems to revert back to Nodejs 5.9.1. What a pain in the ass. I love open source, but times like major upgrades is when I really dislike open source. It’s truly a love-unlove relationship. I guess my only choice right now is to revert back to Nodejs 5.9.1! Hopefully that will work. Feels a bit like WordPress dèja vu.