I was just trying to reply to the tweet above:https://twitter.com/TheLarkInn/status/905810158961307650 …
-
-
The ecosystem is just not good at pipelines that produce reliable source maps. We gotta fix that.
-
A standout: TypeScript. Their sourcemaps are delightful.
-
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
-
Of note: early node people used the fact that sourcemaps was "just a gdoc" as proof that specs weren't really necessary ;)
-
Lol. Well I mean I like the spec process when it's Done Right

-
People need to know what to implement yaknow.
End of conversation
New conversation -
-
-
Unrelated to this thread, afaict, sourcemaps don't handle N -> 1 transformations. Not clear how to handle this in optimizers.
-
What? Sourcemaps were built for N->1 no? Am I misunderstanding?
-
When a single line of final output comes from N different files

-
Ran into this wall when building bundle-buddyhttps://github.com/samccone/bundle-buddy …
-
Dynamic collapsing of multiple duplicated entities becomes very hard to track from bundle to source
-
Yep. I'm combining CSS declarations and i'm building a custom metadata format just to track this.
-
Got it! Thanks :)
End of conversation
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.