On 5/17/17 2:14 PM, Nick Fitzgerald wrote:
In my experience, trying to get anyone to comment or provide feedback on source map RFCs was a huge pain, and it felt to me like nobody (other browser devtools teams, maintainers of compilers targeting JS) cared enough about source maps to get involved or contribute.
OK, but can we at least make sure the browser devtools teams and compilers targeting JS are all on the same page with respect to this stuff? Do we know whether they are or not? This was not indicated in the initial intent in any way.
* Clean up the spec text and any ambiguities it may have; make it a "proper" standard
I think this would be a good thing to do anyway. Otherwise we're likely to end up needing to reverse-engineer other browsers around this stuff.
Specifically, we should have a spec for the sourcemap header, and separately we should have a spec for the sourcemap itself.
And we should actually register the header.
* Pull a wasm on the source map format: create an isomorphic, but much more compact binary format * Add the ability to encode source level scopes, bindings, and a way to recover bindings' values
Those sound good, as part of the spec work... -Boris _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
