Open moltar opened 11 months ago
Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
You can view the code in our open source library in this same repository, why would looking at the js files be better?
When I run a cdk command, and it errors out with a stack trace, I can click the file path in the terminal and open the exact location where the error occurred.
Provided that there are numerous versions and package managers organizing the files (e.g. pnpm uses deeply tested paths), it's not easy to find the source file.
For example, here's a stack trace I am dealing with right now:
Describe the feature
I'd like to see un-minified JS files in the NPM distribution.
Use Case
It's impossible to debug any traces because the entire JS file is in one line.
Proposed Solution
Do not minify the JS distribution. I don't think saving spaces and new lines lead to that much savings, considering the tar balls are gzip'ed.
Other Information
This is what the contents of one file look like:
Acknowledgements
CDK version used
2.91.0
Environment details (OS name and version, etc.)
macOS