Release a debug version of npm packages with sources and source maps

[trivikr]

Is your feature request related to a problem? Please describe.

The source code and source maps were removed in order to reduce publish/install size of AWS SDK for JavaScript (v3). The both help a subset of customers who write their server application in TypeScript and would like to debug SDK code.

• Source code was removed in feat: publish files in dist-* only #2873
• Source maps were removed in feat(tsconfig): remove sourceMap #2867

Describe the solution you'd like

Re-introduce TypeScript source code and source maps in a debug version of SDK.
For example, release version "X.Y.Z-debug" which contains source code and source maps for every version "X.Y.Z" released.

This solution would be similar to #2889

Describe alternatives you've considered

When faced with issues in their TypeScript applications, customers will have to do any of the following to unblock themselves:

• Create an issue on AWS SDK for JavaScript GitHub repo.
• Debug through JavaScript code of the SDK.

Additional context

• Node.js started supporting source maps in Feb 2020.
• Idea discussed prior in another npm package Publish sources and source maps to npm googleapis/google-cloud-node#2867 (comment)

[moltar]

Totally agree with @trivikr here. Source maps are essential for development, debugging (using a debugger) and even production builds, if you want to get any meaningful errors reported.

Without source maps, this is what I am looking at in a debugger (just line noise):

[github-actions]

Greetings! We’re closing this issue because it has been open a long time and hasn’t been updated in a while and may not be getting the attention it deserves. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to comment or open a new issue.

[moltar]

Not stale.

GitHub stale bot considered harmful

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.