-
Notifications
You must be signed in to change notification settings - Fork 327
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
Looking for Node when I am using Bun #1331
Comments
Hi, thanks for reporting. There must must still be some node usage baked in. I will look into this. |
@robisadev Do you have a stack trace? I removed I just implemented |
No, I don't have a stack trace at the moment. I could get one later. Should I? I should have noted that I am using WSL Debian without a node package. |
I'm not sure which part of the codebase is calling
|
Ok, I will send later. |
Sorry this took so long IRL issues. I really have no idea how to get a stack trace. Help! |
Often when npm-check-updates throws an error, it will output the stack trace along with the actual error message. If you're not seeing a stack trace in your terminal when you get this error then unfortunately there is no easy way to turn it on. It could be something in my code that is catching the error and logging the error message but neglecting to log the stack trace. If the error were occurring on my machine, I would clone, build, and run npm-check-updates from source and add some Please try the following and let me know the output:
|
216 | Object.assign(this.options.headers, source.headers);
610 | }
|
Awesome, thanks. It looks like there are two different errors occurring. The first is related to the The second error, |
npm-check-updates
node >= 14.14
bun 1.0
Steps to Reproduce
ncu
orbun npm-check-updates
Current Behavior
Returns
/usr/bin/env: 'node': No such file or directory
Expected Behavior
npm-check-updates to run correctly using bun
The text was updated successfully, but these errors were encountered: