-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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 ignores proxy and registry configs #2060
Comments
@yousifalraheem can you try updating your version of |
@darcyclarke I am on npm 7.4.2 and Node 15 and I am still facing the same issue. I am behind a proxy. |
I've just attempted this. Using |
@thirteen-io fails how? using “latest” right now installs npm 6. |
@ljharb Sorry for not being clear. You are also correct regarding the latest release... totally my mistake sorry. I thought latest was using npm 7. It is at least a temporary workaround for now if you absolutely need the outdated command. |
@thirteen-io Using npm 6 is not a workaround if you want to use workspace which only available on npm 7. My workaround is npm-check-updates. It updates packages in package.json to latest version and I just diff the versions change. |
Current Behavior:
Runing
npm outdated
will throw an error ignoring the proxy and registry configurations. After upgrading to npm 7, I was unable to runnpm outdated
anymore.Expected Behavior:
Should work as intended showing the outdated dependencies.
Steps To Reproduce:
Steps to reproduce the behavior (You need to run this behind corporate VPN and registry):
package.json
that has dependenciesEnvironment:
Screenshots
The text was updated successfully, but these errors were encountered: