We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What is the Problem Being Solved?
ses
ships bundles, yet it ships no source maps. This can make debugging more challenging than necessary when consumingses
via a CJS package.Description of the Design
As part of the build process for
ses
,*.js
indist/
should have an associated*.js.map
file.These files should be shipped when
ses
is 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
The text was updated successfully, but these errors were encountered: