You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
npm is producing incorrect or undesirable behavior.
Other (see below for feature requests):
What's going wrong?
npm warned me that there was a new minor version available (6.0.1 → 6.1.0), so I installed it, and after installing it, npm warned me that there was a new minor version available.
I realize it's doing this because the version of npm that's running is the old version, but it sure would be nice if it was smart enough to realize I was installing the new version and therefore it should suppress the new version warning.
How can the CLI team reproduce the problem?
Have npm 6.0.1 installed and run npm install -g npm.
Why would I have to restart my terminal at all? I'm not using nvm or anything like that. I'm just using a vanilla global install of npm.
This is a red herring anyway, because it doesn't even matter what happens after the upgrade is complete. I'm not complaining that the new version isn't available. I'm complaining that npm itself is warning me that there's a new version, like it does, except it's doing so in response to me telling it to install the new version.
I'd paste the output I'm talking about but I'm not sure how to reproduce it. I just downgraded my npm install and then used it to install another package and it's not giving me the "new minor version available" warning, so I don't know what triggers that.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm opening this issue because:
What's going wrong?
npm warned me that there was a new minor version available (6.0.1 → 6.1.0), so I installed it, and after installing it, npm warned me that there was a new minor version available.
I realize it's doing this because the version of npm that's running is the old version, but it sure would be nice if it was smart enough to realize I was installing the new version and therefore it should suppress the new version warning.
How can the CLI team reproduce the problem?
Have npm 6.0.1 installed and run
npm install -g npm
.supporting information:
npm -v
prints: 6.0.1node -v
prints: v8.11.3npm config get registry
prints: https://registry.npmjs.org/The text was updated successfully, but these errors were encountered: