it would be awesome if SST neatly handled source map output for us, so we don’t have to write our own solutions (esbuild plugins, etc). in other words, when I deploy code/services (not the stacks), it’s all written to a folder w/ the exact same folder hierarchy, and

.js

and

.js.map

files are written there. that way it’s super easy to just upload those to Sentry/wherever in one shot

Yeah agreed. (For @Frank, we might need to talk about this. I remember originally I had tried to make sure that the source maps were shipped inline.)

This is a great suggestion! +1.

@Jay oh i see. which file do I need to look at to check?

@Frank yeah let’s talk about it