-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Node.js child_process compatibility #595
Comments
I don't believe bun supports |
I landed upon this by running a Node.js script that uses Commander, and the Commander package prints this same error. Commander is a very popular package for CLI tools. |
This seems to be an issue using jsdom also.
error: Cannot find package "child_process" from "/Users/thee/git-repo/bun-migrate/scraper/node_modules/jsdom/lib/jsdom/living/xhr/XMLHttpRequest-impl.js" |
If you need child_process now, you can use 3rd package like |
I got this issue while using commander.js (Cannot use bun with commander..) |
I am working on this. |
How's your progress? 🙏 |
@xhyrom might have to assign someone else to this please. Not having |
I already talked to Jarred about switching my progress to someone else because I have school now. Although, he has not replied yet. Now, there should be people getting paid to do this stuff, so you'll most likely see child_process soon. |
@Jarred-Sumner Any update on Re: https://twitter.com/jarredsumner/status/1579898972650381312 |
#1424 👀 |
This has been implemented as of Bun v0.3.0 🎉 |
Version
0.1.3
Platform
Darwin dgreene-mbp 21.5.0 Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:22 PDT 2022; root:xnu-8020.121.3~4/RELEASE_X86_64 x86_64
What steps will reproduce the bug?
Repo case: https://codedamn.com/playground/--6R64znbeUkhqixLdUX_
If that doesn't work:
Make a file with just this one line:
Save it as
child.js
.How often does it reproduce? Is there a required condition?
Just need to import
child_process
.What is the expected behavior?
Child process loads.
What do you see instead?
Result:
Additional information
Note this is not the same error as when a module has not been installed or is an internal module not yet supported. That would look like this:
The text was updated successfully, but these errors were encountered: