On-disk module sources should be transparent to a developer while debugging in VSCode

[kriskowal]

What is the Problem Being Solved?

Currently, when debugging code that is being executed via local use of bundleSource and importBundle, the developer sees the code through the combined lenses of static-module-record and evasive-transform transformations. Their breakpoints do not line up, spacing varies sometimes. The bundle cannot contain a source map or source URL since these vary depending on the physical layout of a developer’s file storage and bundles should have the same integrity hashes regardless of where they are built. However, a bundle can refer indirectly using the hashes of the source or target code and the bundle importer can introduce source URLs and source map URLs before evaluation. Debugging has distinct design criteria from auditing #2117 but some solutions may provide adequate coverage over both.

Description of the Design

Security Considerations

Scaling Considerations

Test Plan

Compatibility Considerations

Upgrade Considerations