-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
[BUG] npm outdated no longer exits with code 1 if outdated #2556
Comments
I'm running into the same bug with: edited: I was in the wrong terminal when I initially ran my node -v and npm -v 😞 ; these values are from the same terminal as the non-responsive command. |
Based on a cursory search, it looks like this is the PR where the exitCode was removed - 3743a42#diff-fcab44373f1f924f030ce92d009f10ab53d45e7a55422870b55f3c7f8af1796d |
@metasean: Nice catch! @claudiahdz @ruyadorno: Was there a reason for the exit code change? |
Not sure, if this is the same feature. nodejs version: v14.16.0 nodejs version: v15.14.0 Besides "Location" should be "project-04" where as "Dependend by" should be "example-project-00" I guess. The later is the projects name within package.json in directory project-04. |
Any updates on this? |
Did not check. |
Finally got around to just doing it myself 🙂 |
#3799 has been merged! Closing. |
Current Behavior:
Exits with code
0
.Expected Behavior:
Exits with code
1
.Steps To Reproduce:
This echos
0
and not1
.Environment:
OS: MacOS Catalina
Node: v15.7.0
npm: 7.4.3
When I run the same script with:
OS: MacOS Catalina
Node: v13.0.1
npm: 6.14.0
I get the output of
1
at the end as expected.The text was updated successfully, but these errors were encountered: