On Wed, Mar 12, 2014 at 2:00 PM, Nick Fitzgerald wrote:
> If a debug format for targeting JavaScript were to be standardized, it
> should do more than simply file/line/column translation. My thoughts
> on this subject outgrew an email reply, so I have collected them here:
> http://fitzgeraldnick
I agree that the current source maps format does a poor job of
handling many translation/transpiling/js-as-compilation-target
scenarios. I do think it is worthwhile to try and build on the
existing format instead of reinvent it or significantly overhaul it,
though. The things it does, it does a pre
> 4) Browsers are still all over the place in how they report Error stack trace
> information.
We (Firefox Developer Tools) purposefully don't expose source mapped
stacks to the web because it would require adding some kind of API to
know when source maps are done being fetched or blocking(!) on
3 matches
Mail list logo
