Skip to content
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

Improve error codes on sigsegv fault #9301

Closed
isakgustavsen opened this issue Mar 7, 2024 · 5 comments
Closed

Improve error codes on sigsegv fault #9301

isakgustavsen opened this issue Mar 7, 2024 · 5 comments
Labels
bug Something isn't working needs repro Needs an example to reproduce

Comments

@isakgustavsen
Copy link

What is the problem this feature would solve?

The current fault does not expose why a build, fails but simply that it does. When switching to pnpm it outputs usable codes.

What is the feature you are proposing to solve the problem?

improve this code:
Error: Command "bun install" exited with SIGSEGV

to something like this:
ERROR: Big integer literals are not available in the configured target environment ("es2019")

This is the same codebase ran on Bun and PNPM

What alternatives have you considered?

No response

@isakgustavsen isakgustavsen added the enhancement New feature or request label Mar 7, 2024
@Electroid Electroid added bug Something isn't working needs repro Needs an example to reproduce and removed enhancement New feature or request labels Mar 7, 2024
@Electroid
Copy link
Contributor

Could you provide your package.json / any commands you ran so we can try to reproduce this?

@isakgustavsen
Copy link
Author

isakgustavsen commented Mar 7, 2024

package.json
PNPM output
Bun output

it was run on vercel so they might also have something to do with it. The full error points to it happening because of the 'vue-email/nuxt' package, but i have attached the log in case there is info im not seeing

@isakgustavsen
Copy link
Author

Working on a reproduction now

@paperdave
Copy link
Member

related but i dont think i have an issue: i want to rebuild the crash handler to be more useful, so that we could resolve the crash and hopefully reduce the need for reproductions.

@Jarred-Sumner
Copy link
Collaborator

We very likely fixed this. Please let us know if you're still running into it sometime in the next week and we'll re-open the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs repro Needs an example to reproduce
Projects
None yet
Development

No branches or pull requests

4 participants