Memory usage can be lower, but the bundler framework matters here. Preprocessing like minify+constant fold saves more parse/mem in my exp
TLDR: if you bundle your modules, you'll hit all the caveats you hit when trying to bundle node modules for the browser.
-
-
We have a good excuse to deal with the limitations when bundling for the browser, but less good excuse when you have actual node.
-
I think this calculus changes with es2015 modules, but we're a while away from bundles composed entirely of es2015 source.
-
I think even with JS modules the bundling will be a worse dev experience. E.g. having to deal with source maps.
-
Source maps need to get better.
-
The ecosystem is just not good at pipelines that produce reliable source maps. We gotta fix that.
-
A standout: TypeScript. Their sourcemaps are delightful.
-
Lol we need a sourcemap spec. Not just a gdoc. Not down playing the work. But implying a revisit strongly needed to be etched in W3C tablets
-
Of note: early node people used the fact that sourcemaps was "just a gdoc" as proof that specs weren't really necessary ;)
- 2 more replies
New conversation -
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.