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

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. #291

Closed
cgreening opened this Issue Apr 27, 2016 · 22 comments

Comments

@cgreening
Copy link

cgreening commented Apr 27, 2016

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

This comment has been minimized.

Copy link
Collaborator

Americas commented May 2, 2016

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

@cgreening

This comment has been minimized.

Copy link

cgreening commented May 2, 2016

"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

This comment has been minimized.

Copy link
Collaborator

Americas commented May 3, 2016

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.

sequelize-cli@2.4.0 /home/prl/Projects/Sequelize/cli
├─┬ fs-extra@0.30.0
│ └── graceful-fs@4.1.2 
├─┬ gulp@3.9.1
│ └─┬ vinyl-fs@0.3.14
│   ├─┬ glob-watcher@0.0.6
│   │ └─┬ gaze@0.5.2
│   │   └─┬ globule@0.1.0
│   │     └─┬ glob@3.1.21
│   │       └── graceful-fs@1.2.3 
│   └── graceful-fs@3.0.8 
├─┬ mocha@2.4.5
│ └─┬ glob@3.2.3
│   └── graceful-fs@2.0.3 
└─┬ sqlite3@3.1.3
  └─┬ node-pre-gyp@0.6.25
    ├─┬ tar@2.2.1
    │ └─┬ fstream@1.0.8
    │   └── graceful-fs@4.1.3 
    └─┬ tar-pack@3.1.3
      └─┬ fstream@1.0.8
        └── graceful-fs@4.1.3 
@cgreening

This comment has been minimized.

Copy link

cgreening commented May 3, 2016

@hgwood

This comment has been minimized.

Copy link

hgwood commented May 13, 2016

See also mochajs/mocha#2111.

@dansef

This comment has been minimized.

Copy link

dansef commented Jun 17, 2016

(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 graceful-fs@4.1.4

@hgwood

This comment has been minimized.

Copy link

hgwood commented Jun 19, 2016

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

@nonmadden

This comment has been minimized.

Copy link

nonmadden commented Jun 22, 2016

I waiting for v6 stable

@pjoshi0788

This comment has been minimized.

Copy link

pjoshi0788 commented Jun 22, 2016

how update graceful-fs

@chrisfosterelli

This comment has been minimized.

Copy link

chrisfosterelli commented Jun 22, 2016

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

@trevordmiller

This comment has been minimized.

Copy link

trevordmiller commented Aug 2, 2016

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

@gwiant

This comment has been minimized.

Copy link

gwiant commented Aug 4, 2016

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

@bateller

This comment has been minimized.

Copy link

bateller commented Aug 5, 2016

@gwiant - Same here.

@gwiant

This comment has been minimized.

Copy link

gwiant commented Aug 5, 2016

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

@nchery nchery referenced this issue Aug 17, 2016

Closed

Can't start gulp #11

@ryanaltvater

This comment has been minimized.

Copy link

ryanaltvater commented Aug 23, 2016

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

@felixfbecker

This comment has been minimized.

Copy link

felixfbecker commented Aug 28, 2016

Thank you @thefonso, deleted the link.

@felixfbecker

This comment has been minimized.

Copy link

felixfbecker commented Aug 28, 2016

Guys it is just a warning. The CLI still works. More details can be found here gulpjs/gulp#1571

@btmurrell

This comment has been minimized.

Copy link

btmurrell commented Oct 12, 2016

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

This comment has been minimized.

Copy link

vshar6 commented Feb 9, 2017

Hi

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

image

@maketroli

This comment has been minimized.

Copy link

maketroli commented May 29, 2017

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

This comment has been minimized.

Copy link

progcode commented Aug 11, 2017

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

@antrez770

This comment has been minimized.

Copy link

antrez770 commented Nov 9, 2017

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment