You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
I'm not exactly sure yet what would happen with Node.js 6, but most likely it would just print deprecation messages. If the warning gets reverted or turned into an error prior to Node.js v6 release (which I personally find unlikely), then v6 will hard break too.
This package still has 24335 downloads/month.
The change is a one-liner and most likely requires only testing.
It's up to you to decide.
Note that I'm not a user of component, I just filed identical issues to several popular packages that depend on the broken graceful-fs version.
I also realized there are so many downloads, but I never trust those stats on npm.
I think if anyone is really using component in production which sounds little legacy to me, then you would also stick to an old node.js version.
Testing and the fragmentation of component into many npm modules makes testing and releasing not so easy.
graceful-fs
versions lower than v4 reevaluate nativefs
module source, which is not supported.You should update your
graceful-fs
dependency to v4 or later.Tracking issue: nodejs/node#5213.
The text was updated successfully, but these errors were encountered: