What nobody's answering for me: what is the perf for all node code bundled into single bundle vs w/o
-
-
I was just trying to reply to the tweet above:https://twitter.com/TheLarkInn/status/905810158961307650 …
-
Correct. I've seen native module reso times cut down considerably for webpack by bundling webpack and running it. But didn't know nuance lvl
-
I think generally if you can get away with bundling reliably you'll get wins, but caveats:
-
1. During dev mode, when lots of things are changing, the bundling time can swamp the wins.
-
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.
- 9 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.