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

SystemError: null #16078

Open
lorypelli opened this issue Dec 31, 2024 · 0 comments
Open

SystemError: null #16078

lorypelli opened this issue Dec 31, 2024 · 0 comments
Labels
bug Something isn't working confirmed bug We can reproduce this issue needs triage

Comments

@lorypelli
Copy link

What version of Bun is running?

1.1.42+50eec0025

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What steps can reproduce the bug?

https://github.com/lorypelli/server repository running scripts/index.ts both with bun and deno (just because node doesn't support typescript out-of-the-box)
https://npmjs.com/fcy (npm version of that)
I'm using node:child_process

What is the expected behavior?

it should work in both cases, when doing bun scripts/index.ts and bunx fcy

What do you see instead?

You can see that bun prints SystemError: null if hitting CTRL + C when asked if using default options, while deno prints Error: Command failed.
But if instead I try bunx fcy (using npm version linked above), it prints the same as deno, so it does work

Additional information

No response

@lorypelli lorypelli added bug Something isn't working needs triage labels Dec 31, 2024
@pfgithub pfgithub added the confirmed bug We can reproduce this issue label Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working confirmed bug We can reproduce this issue needs triage
Projects
None yet
Development

No branches or pull requests

2 participants