TLDR: if you bundle your modules, you'll hit all the caveats you hit when trying to bundle node modules for the browser.
-
-
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 -
A standout: TypeScript. Their sourcemaps are delightful.
1 reply 0 retweets 5 likes -
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
1 reply 0 retweets 5 likes -
Replying to @TheLarkInn @jankrems and
Of note: early node people used the fact that sourcemaps was "just a gdoc" as proof that specs weren't really necessary ;)
2 replies 0 retweets 0 likes -
Lol. Well I mean I like the spec process when it's Done Right
1 reply 0 retweets 1 like
People need to know what to implement yaknow.
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.