-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
@eslint/object-schema
throws p.stdin.end
is not a function on macOS
#12574
Comments
I also tried to use |
Jarred-Sumner
changed the title
Bun Build failed - TypeError: p.stdin.end is not a function. (In 'p.stdin.end()', 'p.stdin.end' is Infinity)
@eslint/object-schema throws p.stdin.end is not a function on macOS
Jul 16, 2024
Jarred-Sumner
changed the title
@eslint/object-schema throws p.stdin.end is not a function on macOS
Jul 16, 2024
@eslint/object-schema
throws p.stdin.end
is not a function on macOS
Jarred-Sumner
added
macOS
An issue that occurs on macOS
and removed
needs triage
labels
Jul 16, 2024
@190n Are you looking into this issue? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of Bun is running?
1.1.20+ae1948925
What platform is your computer?
Darwin 21.5.0 arm64 arm
What steps can reproduce the bug?
Description:
I tried to build the packages within the Eslint Rewrite. When using Node.js,
npm run build
functioned correctly on both Windows and macOS. However, when I used the commandbun run --bun build
on Windows, it performed as expected, whereas on macOS, I encountered the following error:Steps:
npm install
bun run --bun build
What is the expected behavior?
The packages should be built successfully without any errors.
What do you see instead?
Instead I got the below error:
Additional information
It is failing in CI as well - eslint/rewrite#87
When I used the
bun run --bun build
command to build each package individually, it worked as expected.The text was updated successfully, but these errors were encountered: