(honestly haven't heard a single compelling argument for ES modules in Node in the first place, but hmmm that's probs just me)
-
-
Replying to @yoshuawuyts
people keep on telling me that ES modules will make browser bundles smaller (something something tree shaking)
1 reply 0 retweets 0 likes -
Replying to @hackergrrl @noffle
yeah, that's nonsense - static analysis is possible using `require()` already (as evidenced by browserify doing that for bundling
)2 replies 0 retweets 0 likes -
Replying to @yoshuawuyts
does browserify already do this? found https://github.com/substack/node-browserify/issues/1379 …
1 reply 0 retweets 0 likes -
Replying to @hackergrrl @noffle
yeah, the require() tree is traversed and imports are passed in which is needed to create a bundle - otherwise no bundling
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
maybe I've misunderstood? e.g. https://gist.github.com/noffle/4a1fa04601d24a99d95af38f6fcc26b7 … doesn't cull the unused exports
1 reply 0 retweets 0 likes -
Replying to @hackergrrl @noffle
that is correct. Browserify doesn't, but it could (!) - I mean it more like this: https://gist.github.com/
2 replies 0 retweets 0 likes -
Replying to @yoshuawuyts
ah; misparsed you -- thought you were saying it already happened
1 reply 0 retweets 0 likes -
Replying to @hackergrrl @noffle
haha, what I'm saying is: we can make it happen


1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
point taken. it doesn't sound too hard to get something like your example *mostly* working today
1 reply 0 retweets 1 like
oooh, I'd be heaps interested in testing that out! :D
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.