fix(astro): prevent sentry from externalized#9994
Conversation
a184ecf to
fcb1fd5
Compare
fcb1fd5 to
dd338b4
Compare
|
Just applied the changes to my repo and it doesn't seem to be working. AFAIK, You can verify this by printing out the |
|
@billykwok I thought vite was using esbuild only as a transpiler. Otherwise any rollup/vite plugins would have a hard time working... |
There was a problem hiding this comment.
I think the change looks good, generally. +1 on trying to limit the id modification to our @sentry/astro package.
However, I'm a bit unsure if this is enough to get the server side working with CF pages. None of our Fullstack SDKs are compatible with edge/WinterCG runtimes (except for NextJs with Vervel Edge), which I believe also comes down to our general problems with ESM support and the require statements in our http integration and Node transport. I guess we can try though!
One request: Let's guard adding the plugin similarly to how we guard adding the Sentry Vite plugin (sourcemaps) after introducing the enabled option in #10007. No need to add the plugin if Sentry is disabled.
dd338b4 to
0544181
Compare
size-limit report 📦
|
Fixes #9777