163

Recently I've made a switch to Node v.6, and It started creating more and more problems with running normal builds grunt/gulp/webpack

For example:

$ gulp [14:02:20] Local gulp not found in ~/_Other/angular-2-ts/angular2-seed [14:02:20] Try running: npm install gulp

while gulp and all other plugins and modules are installed (and even re-installed via rm -rf node_modules) in /node_modules folder.

Most of those errors have line like

(node:42) 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.

with 42 as arbitrary number

Like in that issue I've submitted - in angular2-seed repo https://github.com/mgechev/angular2-seed/issues/902

What I've tried to do is downgrade to Node v.5 via n (https://www.npmjs.com/package/n) - it worked. Then remove all node_modules folders, then do 

npm info graceful-fs -v 3.3.6

ok, lets upgrade or remove and install new:

npm i graceful-fs@latest npm i [email protected] sudo npm i [email protected] -g

all results in 

npm info graceful-fs -v 3.3.6

So now I am currenlty stuck with graceful-fs 3.3.6 or even worse in some modules dependances, like

$ angular2-seed $ npm install //other lines.. npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.

What could be the strategy here:

  • Manually patch all the deps that contain graceful-fs < 4.0.0?
  • There's some global switch to use specific package version?
  • Reinstall everything?
Improve this question
2
  • I am having same issue with Gulp and some of my modules. I fixed my modules by upgrading the modules to use the latest graceful-fs, but I am not sure there is a solution to fix other modules that have not upgraded yet. Commented May 20, 2016 at 17:01
  • Looks like this won't be fixed in Gulp 3.x and you will have to upgrade to Gulp 4.x github.com/gulpjs/gulp/issues/1571 Commented Jun 1, 2016 at 18:18

11 Answers 11

Reset to default
170

I had this problem and I was able to fix this by updating npm

sudo npm update -g npm

Before the update, the result of npm info graceful-fs | grep 'version:' was:

version: '3.3.12'

After the update the result is:

version: '3.9.3'
Improve this answer
Sign up to request clarification or add additional context in comments.

6 Comments

Thanks @Jorge. This helped fix the problem. I am still getting [email protected] /path/of/app with [email protected] highlighted every time I run npm install in my app directory. but I am living with that for now.
Hi @Geo, same here, look at the answer by analog-nico, we have different versions of the same package because other tools depend strictly on those versions. To get rid of the warning we need to upgrade all of them or look for replacements.
This didn't work for me, I had to run nvm use v6.2.1
Please note that npm info graceful-fs -v returns the version of npm (it is the same as running npm -v) and NOT graceful-fs. To get graceful-fs version, use something like npm info graceful-fs | grep version:.
@Asimov This worked for me too. Also, if you reinstalled NodeJS recently (I installed Node through the package on their website and then replaced it with the one from homebrew) run rm -rf node_modules && npm install in the project home folder.
|
73

Type npm list graceful-fs and you will see which versions of graceful-fs are currently installed.

In my case I got:

npm list graceful-fs @request/[email protected] /projects/request/promise-core +-- [email protected] | `-- [email protected] | +-- [email protected] | | `-- [email protected] | | `-- [email protected] | | `-- [email protected] | | `-- [email protected] <==== !!! | `-- [email protected] `-- [email protected] +-- [email protected] | `-- [email protected] | `-- [email protected] | `-- [email protected] | `-- [email protected] `-- [email protected] `-- [email protected] `-- [email protected]

As you can see gulp deep down depends on a very old version. Unfortunately, I can't update that myself using npm update graceful-fs. gulp would need to update their dependencies. So if you have a case like this you are out of luck. But you may open an issue for the project with the old dependency - i.e. gulp.

Improve this answer

4 Comments

FYI, in your specific example, gulp won't change it in version 3 but only in version 4: github.com/gulpjs/gulp/issues/1571
this was it for me, final push to remove gulp
In my case, the pre-v4 graceful-fs module dependency was coming from npm itself (version 3.10.3) via [email protected]. I didn't see this until I listed the global graceful-fs dependencies using npm list -g graceful-fs.
This helped me solve it. My graceful-fs package was up-to-date, but a few other packages still relied on an older version.
21

Solved this bug with reinstall gulp

npm uninstall gulp npm install gulp
Improve this answer

3 Comments

Sounds like gulp have fixed this issue - couldn't remember if I installed gulp with --save-dev or not before but your way worked from my project folder.
Fixed the issue for me too
Yeah, looks like an older Gulp dependency problem.
1

Deleting node_modules folder contents and running 

npm install bower npm install

solved the problem for me!

Improve this answer

Comments

1

As described here, you can also attempt the command

npm cache clean

That fixed it for me, after the other steps had not fully yielded results (other than updating everything).

Improve this answer

Comments

1

Just to point out that cordova brings in it's own npm with the graceful-fs dependency, so if you use Cordova make sure that it is the latest so you get the latest graceful-fs from that as well.

Improve this answer

Comments

1

I was able to fix it by:

  1. updating by package.json
  2. deleting the node_modules folder
  3. executing npm install
Improve this answer

Comments

0

if you are running nvm you might want to run nvm use <desired-node-version> This keeps node consistent with npm

Improve this answer

Comments

0

Or try to update node:

brew upgrade node

If it is installed with brew (like in my case). sudo npm update -g npm did not solve the "same" problem for me.

Improve this answer

Comments

0

The report says : a file is missing in ... vendor/win32-x64-48/binding.node

I looked for the binding.node file and I find it in...

https://github.com/sass/node-sass-binaries

Copy the correct file with the name binding.node and it works.

Improve this answer

Comments

0

In the case of my Cordova-project, uninstalling and installing cordova -g fixed the problem for me.

npm uninstall -g cordova npm install -g cordova
Improve this answer

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.