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

fstream dependency is old, in turn depends on old deprecated version of graceful-fs #13

Open
robogeek opened this issue Mar 26, 2016 · 5 comments

Comments

@robogeek
Copy link

When I npm install node-unzip-2 this message is printed:

npm WARN deprecated [email protected]: graceful-fs version 3 and before will fail on newer node releases. Please update to graceful-fs@^4.0.0 as soon as possible.

This package depends on an old version of fstream (0.1.21) which in turn depends on an old version of graceful-fs (3.0.2)

The current fstream version (1.0.8) depends on a newer version of graceful-fs (4.1.2).

@apydo
Copy link

apydo commented Apr 14, 2016

Could you please update to the current fstream to avoid the old graceful-fs 3 warning.

@apydo
Copy link

apydo commented May 3, 2016

Here we are :

npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v6.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.

@scarletsky
Copy link

@glebdmitriew
Hello, I've got the same warning because fstream package is outdate.
Could you please upgrade fstream ?

@ChALkeR
Copy link

ChALkeR commented Jul 20, 2016

Note: that warning is soon to be reverted and would be turned into a throw.

Tracking: nodejs/node#5213

I mean the runtime warning fs: re-evaluating native module sources is not supported., not the install-time warning, of course.

@chriskinsman
Copy link

I am stuck with this also. Has anyone forked and updated this yet?

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

Successfully merging a pull request may close this issue.

5 participants