does

.build/

always contain the most recent set of

.js

and

.js.map

files after a build or deploy? in other words, is that a reliable place to have sentry-cli grab source & source maps from to upload to Sentry?

Yes,

.build

at the root gets wiped out on every

sst

command

weird.. I could’ve sworn

.build

had an exact copy of my folder structure when I last deployed. but now it looks like this:

.build/src-services-rest-api-functions-get-tags-main-1628882225462/get-tags.js.map
.build/src-services-rest-api-functions-get-tags-main-1628882225462/get-tags.js
.build/cdk.out/asset.1e4834229dbb0f7d65a19828ce990b83a23d51170c0d74e5d877c1321a2c25d0/get-tags.js.map
.build/cdk.out/asset.1e4834229dbb0f7d65a19828ce990b83a23d51170c0d74e5d877c1321a2c25d0/get-tags.js

I’m not really sure how I’d script something to look in the right place for source maps 🤔 any advice here? or should I just write an esbuild plugin to copy .js and .js.map files to a different folder that I control?