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
Hi. grunt-google-cdn is currently #10 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.
@3
For node 10+ support, graceful-fs has to be updated to 4+. So all our dependencies using graceful-fs have to be updated to a version that uses @4.
grunt-google-cdn is also affected but has not been updated in 6 years. See btford/grunt-google-cdn#71
Since it's not a must-have, I've removed it.
Hi.
grunt-google-cdn
is currently#10
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
andgraceful-fs@4
are ok and would not be broken by this, but arequire()
ongraceful-fs@2
orgraceful-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
orgraceful-fs@3
in runtime — you are affected.Tracking: nodejs/node#5213.
The text was updated successfully, but these errors were encountered: