S3 bucket having issues for StaticSite - anybody e...
# sst
j
S3 bucket having issues for StaticSite - anybody else seeing this issue?
f
Hey @Jack Fraser does the error go away on redeploy?
j
@Frank No. I even tried deleting the stack and then fresh deploy. Other new stages are fine though 🤷
@Frank any other ideas? just happened on another stage
@Frank could it be a memory issue on Seed? I had just turned on sourcemaps when I starting getting the isssue.
f
hmm.. the Lambda function that’s doing the s3 deployment is failing.
Do u know if the
xxxxportal-patient
custom resource comes from the
StaticSite
construct?
j
@Frank Seems this line in package.json was causing the issue
"postbuild": "mkdir dist_source_maps; mv dist/*.map dist_source_maps/",
I was moving the .map files out of our main dist (then uploading the .map files to bugsnag via the stack index.ts file)
j
Hey @Jack Fraser just following up here, did you manage to fix this?
j
@Jay did not manage to sort
j
Is it that the
postbuild
script is failing on Seed?
j
the postbuild script itself is running ok, but the stack fails. Guessing it might be something to do with me moving some of the files out of the dist folder in the postbuild script. Any other ideas how to upload map files to bugsnag but not to upload them to s3 etc ?
j
I think @Sam Hulick was doing something similar with uploading the source maps to Sentry.
He might’ve shared his setup on Slack. Might be worth a quick search.