Cli: 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.

[cgreening]

Using node v6.0 this error is reported:

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

[Americas]

node v6 is still not supported in many packages. Consider going back to v5.

[cgreening]

"Node.js v5 will continue to be supported for the next two months in order to give developers currently using v5 time to transition to Node.js v6."

https://nodejs.org/en/blog/release/v6.0.0/

[Americas]

Here is a tree of sequelize dependencies that use graceful-fs. If you want this warning to disappear faster, contact the maintainers and ask them to upgrade their dependencies so they will only use graceful-fs version 4 or greater. Afterwards, the warning will disappear.

[email protected] /home/prl/Projects/Sequelize/cli
├─┬ [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]
    │   └── [email protected] 
    └─┬ [email protected]
      └─┬ [email protected]
        └── [email protected] 

[cgreening]

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

[hgwood]

See also https://github.com/mochajs/mocha/issues/2111.

[josephwambura]

(node:3528) 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.
i am using [email protected]

[hgwood]

@dansef It is still possible that graceful-fs@<4 appears somewhere in your dependency tree.

[arnonhongklay]

I waiting for v6 stable

[pjoshi0788]

how update graceful-fs

[chrisfosterelli]

@arnonhongklay V6 is stable. They no longer use the term stable, and instead use "current" (which 6 is right now).

[trevordmiller]

Upgrading npm to latest removed these errors for me: npm upgrade -g npm

[gwiant]

I ran "npm upgrade -g npm" and still have the issue. I am on Node v5. NPM v3.10.6

[bateller]

@gwiant - Same here.

[gwiant]

I'm seeing this in dependencies which I'm not able to update...

[ryanaltvater]

I'm on node v6.4.0 and npm v3.10.6 and still experiencing this issue.

[felixfbecker]

Thank you @thefonso, deleted the link.

[felixfbecker]

Guys it is just a _warning_. The CLI still works. More details can be found here https://github.com/gulpjs/gulp/issues/1571

[btmurrell]

yes, it's just a warning, but when you're running a script that has messages you care about this is a very large amount of annoying noise.

that said, for me, on v6.2.1, @trevordmiller 's solution to run npm upgrade -g npm solved it for me. thanks @trevordmiller !

[vshar6]

Hi

I am still finding this issue. Request to help. My version details are in the below screenshot.

[m-ret]

In order to remove those errors I had to run this in the terminal curl -L https://www.npmjs.org/install.sh | sh then upgraded npm to the latest and put node on version 6.0.0

I am using n, I switch from node 5 to 6, I ran the typical node rebuild node-sass and it shows the error:

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

That error/warning doesn't show up anymore once I installed node 6.0.0.

I think that one of the main issues here, is the node version that you used when the project begun, so the fixes of one dev wouldn't the same for the other devs.

Is very hard to believe that every time we switch to a new version of node or any other package is upgraded, we have to live this hell, I've been trying to make my project to run for around 3 hours. It's ridiculous.

[progcode]

I'm on node v6.11.2 and npm v3.10.10 and still experiencing this issue.

[antrez770]

Hi, Did somebody resolve this issue?
Is somebody solved this problem with update the version of node? Any comments?