1. During dev mode, when lots of things are changing, the bundling time can swamp the wins.
-
-
Replying to @wycats @TheLarkInn and
2. Before ES2015 modules, it's difficult to reliably bundle, so your bundled modules will often fail without manual intervention.
1 reply 0 retweets 3 likes -
Replying to @wycats @TheLarkInn and
3. (2a?) Patterns like "load all my tests" are trickier in module world.
1 reply 0 retweets 2 likes -
Replying to @wycats @TheLarkInn and
TLDR: if you bundle your modules, you'll hit all the caveats you hit when trying to bundle node modules for the browser.
1 reply 0 retweets 0 likes -
Replying to @wycats @TheLarkInn and
We have a good excuse to deal with the limitations when bundling for the browser, but less good excuse when you have actual node.
1 reply 0 retweets 1 like -
Replying to @wycats @TheLarkInn and
I think this calculus changes with es2015 modules, but we're a while away from bundles composed entirely of es2015 source.
1 reply 1 retweet 2 likes -
Replying to @wycats @TheLarkInn and
I think even with JS modules the bundling will be a worse dev experience. E.g. having to deal with source maps.
1 reply 0 retweets 1 like -
-
The ecosystem is just not good at pipelines that produce reliable source maps. We gotta fix that.
2 replies 0 retweets 3 likes -
I'd also like a more feature rich spec if possible
1 reply 0 retweets 1 like
Yeah, something closer to DWARF (but let's not get ahead of ourselves)
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.