Standardized way of publishing debug files #70
Description
Hi,
I'm currently fighting a few crashes in my electron app related to native modules. Since the stack traces generated by minidump are not very helpful without the debug files generated at build time of the modules, we're having trouble figuring out what the problem is, for example here and here.
If the build pipeline could download the debug files generated by prebuildify (for example .pdb on Windows) and upload it to the Crash Reporting Service (in my case Sentry), it would allow for much easier debugging.
How could this be achieved in a standardized way, so that people don't have to write a separate download script for the debug files of each package?
I don't think it's a good idea to include those files in the publish tarball (for npm for example), because they can be quite big and are (as far as I know) not needed in the application itself but rather for the crash reporting service on the serverside.