Open boneskull opened 1 week ago
ses ships bundles, yet it ships no source maps. This can make debugging more challenging than necessary when consuming ses via a CJS package.
ses
As part of the build process for ses, *.js in dist/ should have an associated *.js.map file.
*.js
dist/
*.js.map
These files should be shipped when ses is published.
none
depends if we have to hand-roll it. if we do, then we should assert the generated source maps are at least valid / parseable.
What is the Problem Being Solved?
sesships bundles, yet it ships no source maps. This can make debugging more challenging than necessary when consumingsesvia a CJS package.Description of the Design
As part of the build process for
ses,*.jsindist/should have an associated*.js.mapfile.These files should be shipped when
sesis published.Security Considerations
none
Scaling Considerations
none
Test Plan
depends if we have to hand-roll it. if we do, then we should assert the generated source maps are at least valid / parseable.
Compatibility Considerations
none
Upgrade Considerations
none