Not quite following the question. Are you asking what the perf impact is of using multiple modules vs combining into one?
-
-
2. Before ES2015 modules, it's difficult to reliably bundle, so your bundled modules will often fail without manual intervention.
-
3. (2a?) Patterns like "load all my tests" are trickier in module world.
-
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.
- 5 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.