I think this calculus changes with es2015 modules, but we're a while away from bundles composed entirely of es2015 source.
-
-
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 -
Replying to @wycats @TheLarkInn and
Speaking as the person responsible for testing sourcemaps in TypeScript when they were first added... a spec would have been REALLY nice
1 reply 0 retweets 3 likes -
*and* they edited it a few times and kept the same version number. Was very confusing. +1 for a spec.
1 reply 0 retweets 2 likes -
All jokes aside, ... can we use DWARF? Is there a blocker on using it?
2 replies 0 retweets 0 likes
We could use DWARF. @fitzgen has proposed it to me before. He also worked on https://crates.io/crates/gimli and related.
-
-
Replying to @wycats @bradleymeck and1 reply 0 retweets 1 like
- 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.