tc39/source-map Issues

Last updated Nov 21, 2024, 5:51:15 AM UTC.

This repository doesn't have the Priority: Eventually label that's used to mark an issue as triaged without giving it an SLO. Until that's added, this summary uses heuristics to guess if each issue has been triaged.

Untriaged

Try to triage issues within . [ More Info ]

Issue Title Within SLO On maintainers' plates for Time left Time past SLO
#19 Unique Debug IDs (Build IDs) for Source Maps ❌
#35 Exit criteria for a hardened specification ❌
#39 Follow-up group meeting ❌
#63 Use JSON destination for fetching source maps ❌
#80 Make 32-bit limit on VLQs more precise ❌
#81 Make index map specification more precise ❌
#93 Specify validation for new features ❌
#95 Make precise what is accepted as an index in, e.g., ignoreList ❌
#101 Generated range of value replaced in the inlined function ❌
#103 Consider reworking "background" section of spec ❌
#105 My dream spec text ❌
#108 Does the HTTP source map header work for CSS files? ❌
#111 Scopes: tweak function example and usage advice ❌
#121 Scopes: When writing the spec text, add a section that we thought about security ❌
#138 Avoid ambiguous "extract a source map comment" algorithms ❌
#139 Extent of mapping segments ❌
#146 Debug IDs Proposal: Should We Define a JavaScript API? ❌
#149 Workflow: Auto-publish all branches to gh-pages ❌
#151 Editorial: Extract 'generatedPosition' and 'originalPosition' structs ❌
#155 Mappings v2: More Efficient Encoding ✔
#156 Editorial: Add CSS to adjust list bullets to match ECMA ✔
#157 Editorial: unify ECMA-262 references ✔