Getting inconsistently failing builds using vite-plugin and Vercel about sentry-javascript-bundler-plugins HOT 5 CLOSED

Hmm, yeah, the symptoms are similar to pnpm/pnpm#4649 I'll try some of the fixes that people mentioned in the comments and I'll report back. Worst case I guess a hacky fix could be to somehow always install @sentry/cli fresh 🤔

from sentry-javascript-bundler-plugins.

Hi, thanks for writing in about this. The build failing non-deterministically seems very weird to me but we had issues with Sentry CLI + Vercel before. Is there anything else in the build logs worth sharing?

from sentry-javascript-bundler-plugins.

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

from sentry-javascript-bundler-plugins.

Hey all 👋🏻 we are experiencing the same issue and there is not much to go after. @hardyjosh any chance you figured out what the issue was?

Our sentry package versions:

"@sentry/react": "^7.50.0",
"@sentry/tracing": "^7.50.0",
"@sentry/vite-plugin": "0.7.2",

The log from vercel build:

[sentry-vite-plugin] Info: Sending error and performance telemetry data to Sentry.
--
13:09:43.770 | [sentry-vite-plugin] Info: To disable telemetry, set `options.telemetry` to `false`.
13:09:43.772 | ✓ 0 modules transformed.
13:09:43.772 | [sentry-plugin] spawn /vercel/path0/node_modules/.pnpm/@[email protected]/node_modules/@sentry/cli/sentry-cli ENOENT
13:09:43.772 | error during build:
13:09:43.772 | Error: spawn /vercel/path0/node_modules/.pnpm/@[email protected]/node_modules/@sentry/cli/sentry-cli ENOENT
13:09:43.772 | at ChildProcess._handle.onexit (node:internal/child_process:283:19)
13:09:43.772 | at onErrorNT (node:internal/child_process:476:16)
13:09:43.773 | at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
13:09:43.780 | ELIFECYCLE  Command failed with exit code 1.
13:09:43.803 | Error: Command "pnpm build && pnpm run sourcemaps:clear" exited with 1
13:09:44.548 | Deployment completed
13:09:44.157 | BUILD_UTILS_SPAWN_1: Command "pnpm build && pnpm run sourcemaps:clear" exited with 1

Okay now that I've put this together, I have actually noticed the part that seems wrong

13:09:43.772 | ✓ 0 modules transformed.

Healthy builds do have a non-zero number there as well as additional logs + rebuild on a deployment that is failing this way seems to produce a healthy build again.

from sentry-javascript-bundler-plugins.

Hmm I assume this is somehow related to the build cache. The Sentry CLI binary, which can't be found here, is installed via a post-install script (trust me I don't like this but fixing this is gonna take a while) and maybe the binary isn't stored across builds.

Maybe it's related to pnpm/pnpm#4649 and is solved by setting side-effects-cache=false in pnpm?

from sentry-javascript-bundler-plugins.