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

graceful-fs@2 and @3 support will be removed soon #2

Open
ChALkeR opened this issue Feb 13, 2016 · 1 comment
Open

graceful-fs@2 and @3 support will be removed soon #2

ChALkeR opened this issue Feb 13, 2016 · 1 comment

Comments

@ChALkeR
Copy link

ChALkeR commented Feb 13, 2016

graceful-fs versions lower than v4 reevaluate native fs module source, which is not supported.
You should update your graceful-fs dependency to v4 or later.

Tracking issue: nodejs/node#5213.

@ChALkeR
Copy link
Author

ChALkeR commented Aug 8, 2016

Hi. traverse-directory is currently #13 in my list of modules that would likely 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.

@ChALkeR ChALkeR changed the title Bump graceful-fs dependency graceful-fs@2 and @3 support will be removed soon Aug 8, 2016
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

1 participant