Vercel build errors in runtime due to Sentry CLI binary for arch not found #1849
Comments
|
Same issue happening here using npm. sveltekit(v1) build on vercel. We didn't upgrade sveltekit when this started happening, so I assume this version got pulled in on fresh install Same issue in |
|
Thank you for reporting this bug, @mcmxcdev. We are looking into it. Just to confirm, are you still able to use |
|
FWIW we can't even downgrade, seems like @sentry/cli is being pulled in: When looking at: https://github.com/getsentry/sentry-javascript-bundler-plugins/blob/main/packages/bundler-plugin-core/package.json#L55 the |
|
@szokeasaurusrex Yes, we locked We haven't investigated further which version after 7.76.0 works and which one doesn't anymore (due to pulling in @sentry/cli@2.22.3) |
|
Can you try redeploying on Vercel without build cache? Thank you! |
|
We're also facing this issue. The workaround has been to peg "@sentry/cli": "2.22.2". Deploys using "@sentry/sveltekit": "^7.84.0", and previous versions were successful by locking this version. |
|
This is caused by a Vercel bug/feature - please see vercel/nft#371 |
|
Faced the same issue, thanks @smart for workaround! |
|
Pegging the version to @sentry/cli": "2.22.2 using pnpm and any version of @sentry/sveltekit worked around the build errors. However, our function is still crashing when being invoked because it's looking for @sentry/cli 2.22.3. From our Vercel logs: It seems like none of the "@sentry/cli" package's optional dependencies got installed. Please make sure your package manager is configured to install optional dependencies. If you are using npm to install your dependencies, please don't set the "--no-optional" or "--omit=optional" flags. Sentry CLI needs the "optionalDependencies" feature in order to install its binary.
at getBinaryPath (/var/task/node_modules/.pnpm/@sentry+cli@2.22.3/node_modules/@sentry/cli/js/helper.js:116:13)
at Object.<anonymous> (/var/task/node_modules/.pnpm/@sentry+cli@2.22.3/node_modules/@sentry/cli/js/helper.js:129:18)
at Module._compile (node:internal/modules/cjs/loader:1256:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
at Module.load (node:internal/modules/cjs/loader:1119:32)
at Module._load (node:internal/modules/cjs/loader:960:12)
at r.<computed>.e._load (/var/task/___vc/__launcher/bridge-server-72TT5FOD.js:1:1574)
at Module.require (node:internal/modules/cjs/loader:1143:19)
at require (node:internal/modules/cjs/helpers:119:18)
at Object.<anonymous> (/var/task/node_modules/.pnpm/@sentry+cli@2.22.3/node_modules/@sentry/cli/js/index.js:4:16)
INIT_REPORT Init Duration: 1083.56 ms Phase: invoke Status: error Error Type: Runtime.ExitError
Error: Runtime exited with error: exit status 1 |
* main: fix: make resolution work fix: bad sentry dep on vercel getsentry/sentry-cli#1849 Revert "chore: major version updates vite" feat: add preconnects for wordpress assets to be downloaded chore: major version updates vite chore: update deps chore: cleanup misc chore: update smui fix: properly order imports/exports fix: add aria roles to resizable divider chore: format code refactor: remove unneeded prettier config lines
|
Sveltekit 2 users would need to downgrade the framework to fix this issue. Is there anyone working on this? Update: I've tried the fix noted above that pins Probably gonna give up here. |
+1 a bummer as both a paid sentry and vercel user if nothing, a guide on a workaround is expected at the very least. |
|
Sorry for the delay here. It'll take a little longer than usual with maintainers being out of office for the holidays. |
|
We've pinged Vercel about this. I'll see if I can find a workaround for this this week. |
|
Someone pointed me here. I'm running SvelteKit + Sentry + Vercel without issue right now. My package manager is Here are some excerpts from {
...
"devDependencies": {
...
"@sveltejs/adapter-auto": "^2.1.1",
"@sveltejs/kit": "^1.27.4",
...
"svelte": "^4.2.3",
...
"vercel": "^32.5.3",
"vite": "^4.5.1",
...
},
"dependencies": {
...
"@sentry/integrations": "^7.91.0",
"@sentry/sveltekit": "^7.91.0",
...
"@sveltejs/adapter-vercel": "^3.0.3",
...
},
...
}and Let me know if that helps or, I'm happy to post more details about our setup |
|
@gwax Thank you for responding. So, I had to nuke my "dependencies": {
+ "@sentry/integrations": "^7.91.0",
+ "@sentry/sveltekit": "^7.91.0",
+ "@sentry/tracing": "^7.80.1",
"luxon": "^3.4.4",
"md5": "^2.3.0",
"natural": "^6.10.4"
- }
+ },
+ "overrides": {
+ "@sentry/browser": "7.80.1",
+ "@sentry/integration": "7.91.0",
+ "@sentry/node": "7.91.0",
+ "@sentry/svelte": "7.91.0",
+ "@sentry/sveltekit": "7.91.0",
+ "@sentry/cli": "2.22.2",
+ "@sentry/utils": "7.80.1",
+ "@sentry/tracing": "7.80.1"
+ },All in all this works... but it feels super brittle. |
|
@Gipetto these dependencies look very problematic. Make sure all dependencies except for the CLI are on the same version. Also |
|
:sigh: So, it turns out that I'm likely an idiot. The part here where I had to nuke or manually edit my package-lock got me to go back and try from the beginning again.
So the folks who have been using Sentry for a while likely still have older known good versions in their lock files. And there's probably more out there like me who didn't think through the correct way to pin a package in NPM or were just moving too fast. |
Have you been able to reach them outside of that GitHub issue? They just renamed it to be specific to |
|
@knd775 I've pinged them on slack but I believe Vercel is on company holiday until the end of the year. I'd prefer if we keep communication about this in the public in any case (i.e. over at vercel/nft#371). |
|
We've released a new version of the CLI Please try it out and let me know if it solved the issue for you. |
|
@lforst can confirm, updating to EDIT: |
|
It does work, but we're also getting these errors. Something is still using the old CLI version |
|
struggled a bit even after upgrading to |
In our When I inspect the (we still can't deploy on vercel) |
|
In your package.json add: "overrides": {
"@sentry/cli": "2.22.2"
}Then either: a. delete your Then re-run |
|
I believe that setting https://kit.svelte.dev/docs/adapter-vercel#deployment-configuration |
I left this comment on the vercel issue, but thought it was worth repeating here:
|
|
This issue should be fixed with the newest version of the |
Environment
@sentry/cliv2.22.3 on Ubuntu 23.10Steps to Reproduce
When attempting to upgrade
@sentry/sveltekitfrom 7.76.0 to 7.83.0, we encounter this runtime error on a Vercel preview deployment URL:The issue is most likely related to https://github.com/getsentry/sentry-cli/releases/tag/2.22.3
The package manager in use is pnpm, optional dependencies are not disabled, and the
.npmrcfile looks as follows:Expected/Actual Result
Deployment should work as usual
The text was updated successfully, but these errors were encountered: