A browserify transform to enable the easy use of bower components in browserify client javascript projects. This can be used in conjunction with deamdify to require AMD components from bower as well.
493
stars
51
forks
source link
graceful-fs@2 and @3 support will be removed soon #86
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.
ChALkeR
commented
7 years ago
Hi.
debowerifyis currently#69in my list of modules that would likely be broken when https://github.com/nodejs/node/pull/6413 lands (which is anticipated to happen before v7.0).Note that
graceful-fs@1andgraceful-fs@4are ok and would not be broken by this, but arequire()ongraceful-fs@2orgraceful-fs@3would 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@2orgraceful-fs@3in runtime — you are affected.Tracking: https://github.com/nodejs/node/issues/5213.