Grunt issue on sailslift - error: Grunt :: (node:6532) fs: re-evaluating native module sources is not supported.

[gustavLatte]

Sails version: 0.12.3
Node version: 6.0.0
NPM version: 3.8.6
Operating system: Windows 10 64bit

---

Hi,

I just upgraded node to it's latest version (6.0.0) and when lifted my sails app i got this error:

error: Grunt :: (node:6532) 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.

Any ideas what it could be?

[stevestock]

Why is this closed. The linked issue is closed too.

I am having this problem as well.

[jimior2]

got same problem here.

[sgress454]

Sorry all, seems like my previous comment didn't post for some reason.

The error message is a little cryptic, but it says it all: the module in question is probably not compatible with Node 6. You can try wiping your node_modules folder, then doing npm cache clean followed by npm install to see if it helps, but the only real solution until new versions come out is probably to downgrade your Node version to something less bleeding edge, or remove the watch task from tasks/register/default.js.

[gustavLatte]

Thanks @sgress454
for me i think i'll just remove the watch task as I kind of researching with Node 6.

[jamilnyc]

For anyone else that stumbles on this. I noticed that I don't get the error when lifting as root
sudo sails lift

[iustin-nita]

Same problem here.

[merianos]

Me too ...

[hgwood]

This is a warning that the program will break in Node 7. See nodejs/node#5102. A dependency is probably using graceful-fs@<4.

[ktravelet]

I'm having this problem as well. This seems to be causing grunt to not inject the dependency files now. Is anyone else having that problem?

running 'npm update graceful-fs' doesnt do anything. I'm thinking updating the top level npm packages will help with the following:

npm update grunt
npm update grunt-contrib-watch

any thoughts before I do this and break my system?

npm ls graceful-fs
├─┬ [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]
└─┬ [email protected] -> /usr/local/lib/node_modules/sails
├─┬ [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]

[icodeforlove]

having the same issue

node v6.0.0
sails v0.12.3

[mounirn]

same issue with node v6.2.0 and sails v0.12.3

[VirtualWolf]

Yep, same problem too, same versions as @mounirn. Makes me sad because I want to use Node 6 to get all the shiny new ES6 features that 5.x doesn't support. :(

[hgwood]

@VirtualWolf Help sails upgrade to grunt 1.0 and grunt-contrib-watch 1.0. That should fix the problem. :)

[kiesman99]

Hello guys I solved this problem on my PC :)

Just install this package: https://www.npmjs.com/package/npm-check-updates

then go into your sails project and type in

ncu

You'll see all the modules you can update.
To update them type in

ncu -u
npm install

And it's done :)

[cburatto]

@kiesman99 thumbs up -- worked here

[parnurzeal]

@kiesman99 working! thx!

[ChALkeR]

Hi. sails is currently #16 in my list of modules that would likely to be broken when nodejs/node#6413 lands (which is anticipated to happen before v7.0).

Note that graceful-fs@1 and graceful-fs@4 are ok and would not be broken by this, but a require() on graceful-fs@2 or graceful-fs@3 would cause an error soon.

That is, runtime warning fs: re-evaluating native module sources is not supported. would be turned into a throw.

If you or your deps use graceful-fs@2 or graceful-fs@3 in runtime — you are affected.

Tracking: nodejs/node#5213.

@sgress454, does this still need more info?

[ChALkeR]

@ktravelet Note that graceful-fs@1 do not trigger the runtime warning and would not be affected. The runtime warning is caused by [email protected] here.

[sgress454]

@ChALkeR do you still get this with the latest on master (published as sails@beta)? All the relevant dependencies should be updated.

[ChALkeR]

@sgress454 Good to know, thanks! I don't personally use sails, and I tested only the @latest of everything. Any ETA? Node.js 7.0 is going to be released in autumn, so the breakage won't happen until then.

[davoscript]

Hey, just in case anyone is checking this. Latest sailsjs version is using grunt 1.0.0 which solved the problem for me.

I updated sails, then created a new temp project and copied the package.json dependencies to my project.