-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@sentry-cli not working with @sentry/vite-plugin when installed with bun #412
Comments
I suspect what might be happening here is that Bun does not run If you do that, does it work? |
Good point, wasn't aware of that. Unfortunately it still does not work with the same error. But I also guess it is the postinstall script or something... |
Going to move this to the bundler plugin repo so we can investigate and look at this deeper. What version of bun are you using to run the command? |
Same problem for me with nextjs. First saw a problem with vercel "error - Sentry CLI binary not found. Source maps will not be uploaded." This lead me to add it as trustedDependencies to run post install scripts but its not working. Current Bun version: 1.0.3 |
Hmm I'm wondering if |
Gave this a retry and now it's working. Not sure what I did different the last time or if it's maybe related to updating bun. Using trustedDependencies works, here are the steps: oven-sh/bun#2998 (comment) |
I am still getting the problem with svelteKit 1.27.6 / vite 4.5 + @sentry/sveltekit. |
@Cluster2a you need to add |
I added all of them.
|
@Cluster2a I recommend just making sure |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/browser
SDK Version
7.57.0
Framework Version
No response
Link to Sentry event
No response
SDK Setup
Steps to Reproduce
Install @sentry-cli and @sentry/vite-plugin with bun and try to run it. Works fine when installed with npm ci, but does not work with bun.
Expected Result
Sourcemaps get generated and uploaded to sentry.
Actual Result
Error: spawn /Users/xxx/Projects/xxx/node_modules/@sentry/cli/sentry-cli ENOENT
The text was updated successfully, but these errors were encountered: