Follow-up group meeting #39
Description
We will be meeting in the next TC39 Tools call to discuss source maps further. This will be May 3rd at 12:00 America/New_York.
If this isn't already on your calendar, you can request an invite in this form (expressing interest in "tools"). That invite will point to the Google Meet call and notes doc.
A draft agenda (additions welcome!):
- Dan: Review goals – are we in agreement with these? Goals for evolving source maps #22
- Workstream – Spec correctness
- Armin: Bikeshed conversion of v3 Convert the source map spec to bikeshed with minor edits source-map-spec#1 https://source-map.github.io/source-map-spec/
- Hubert: Conformance testing Test Suite for Source Maps #15
burndown of issues https://github.com/source-map/source-map-rfc/issues?q=is%3Aissue+is%3Aopen+label%3A%22Workstream%3A+Correctness%22
- Workstream – Naming
- Holger: Variable naming proposal Scopes and variable shadowing #37
- Rob Paveza: Representation of scopes Proposal: Source Maps v4 (or v3.1): Improved post-hoc debuggability #12
- Lilit: Pasta source maps for function names https://github.com/bloomberg/pasta-sourcemaps/blob/master/spec.md
- Chrome, Sentry, replay.io: Share experience with re-parsing source code to find names–pitfalls, room for improvement, etc.
- Workstream – Correlating source maps, compiled scripts and source scripts
- Armin: Debug ID proposal https://github.com/source-map/source-map-rfc/blob/main/proposals/debug-id.md
- Rob: SHA hashes accessible from JS Added debug id proposal #20 (comment)
- Prioritization of workstreams?
- Proposal from Dan: Work on them all at once, but when we have too much on a call agenda, discuss “correctness” first.
- Rationale: This will give us a more solid basis to build features on top of
- Dan: Bring to TC39 and operate as TG4? Co-presenters? Work with a web standards organization #7 (comment)
Remember to join our Matrix channel!