Skip to content
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

Error: 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. #13

Closed
MoOx opened this issue May 2, 2016 · 6 comments

Comments

@MoOx
Copy link

MoOx commented May 2, 2016

Following AtomLinter/linter-eslint#564

Error: (node:1458) 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.
    at ChildProcess.<anonymous> (/Users/MoOx/setup/dotfiles/.atom/packages/linter-eslint/node_modules/atom-linter/node_modules/sb-exec/lib/index.js:36:20)
    at emitTwo (events.js:87:13)
    at ChildProcess.emit (events.js:172:7)
    at maybeClose (internal/child_process.js:818:16)
    at Socket.<anonymous> (internal/child_process.js:319:11)
    at emitOne (events.js:77:13)
    at Socket.emit (events.js:169:7)
    at Pipe._onclose (net.js:469:12)

This appears when I update Node to 6.x.

@steelbrain
Copy link
Owner

steelbrain commented May 2, 2016

Node v6 is a quite buggy release with several bugs in different areas, this is not a problem in this package but in eslint that is not being run under Node v6 or in Node v6 itself. The error stack points out that the error is coming from the stderr of the spawned process.

To resolve this issue, I would recommend you downgrade your node to a more stable version

@Arcanemagus
Copy link
Collaborator

From discussion with @steelbrain it sounds like this is simply being repeated from the stderr of whatever linter you were using at the time. Do you happen to know what file you were editing when this showed up?

@MoOx
Copy link
Author

MoOx commented May 2, 2016

Yeah. It happened for linter-eslint and linter-flow for all my files (private project).

@Arcanemagus
Copy link
Collaborator

Does flow itself work after the update to Node v6?

@MoOx
Copy link
Author

MoOx commented May 2, 2016

It seems to.

@hgwood
Copy link

hgwood commented May 13, 2016

See nodejs/node#5102.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants