Npm WARN deprecated graceful-fs@3.0.8: graceful-fs version 3

Question

I run npm install, but this gives me an error. I also tried to execute the command below before updating. $ npm install npm, and also I updated graceful-fs.

$ npm install -g graceful-fs graceful-fs@4.1.3 C:\Users\RDY672\AppData\Roaming\npm\node_modules\graceful-fs 

The ERROR is as follows:

 $ npm install -g bower@1.3.12 npm WARN deprecated graceful-fs@3.0.8: graceful-fs version 3 and before will fail on newer node releases. Please update to graceful-fs@^4.0.0 as soon as possible. npm WARN deprecated graceful-fs@2.0.3: graceful-fs version 3 and before will fail on newer node releases. Please update to graceful-fs@^4.0.0 as soon as possible. npm WARN deprecated npmconf@2.1.2: this package has been reintegrated into npm and is now out of date with respect to npm npm ERR! cb() never called! npm ERR! not ok code 0 

Answer 1

TL; DR: If necessary, simply delete the files and ignore the obsolescence warnings. If this is not a mistake, this is not your problem.

---

Most likely, this indirectly depends on the outdated version of elegant fs, which depends on the internal Node modules (although this should not). This module, of necessity, largely depends on the details of the Node implementation, but 4.x was written as less fragile in this regard. The API has changed slightly between 3.x and 4.x.

For what it's worth, one count a couple of weeks ago had this module as the tenth most loaded on npm. I do not see this changing. And due to the large share of the use of this module (npm itself is indirectly dependent on the outdated version), Node has already installed a temporary fix in which they try to get people to disconnect from the internal modules .

So do not worry if you do not get errors from him. I usually ignore these obsolescence warnings, as they are already very well known.

Answer 2

npm install -g graceful-fs graceful-fs@latest works for me.

This installs the latest version of elegant fs!

Answer 3

You do not need to worry about this, and there is nothing wrong with the dependency, as this only affects development. The gulp team is aware of the problem.

We know about a nice fs warning when installing gulp 3.x.

This is due to: 1. our graceful fs devDependency 2. dependency vinyl-fs

Both of which we cannot update due to changes that violate the API.

There is nothing wrong with dependency, especially since it is used only in development. We will update or delete it in gulp 4 and the message will disappear.

https://github.com/gulpjs/gulp/issues/1571

Answer 4

I agree with all the comments that it does not affect him at all. But in case you want to update.

First check which versions you already have graceful

 $ npm ls graceful-fs 

and if you do not have the latest version, install it

 $ sudo npm install -g graceful-fs graceful-fs@latest-version 

Answer 5

I use the Windows platform and Homestead. The following commands work for me in the console:

 npm install --no-bin-links gulp npm rebuild node-sass gulp