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 outdated reports which versions can be updated. However, when an exact version is provided as a dependency, npm outdated will never show that it can be updated.
In my mind, this should also report if a version has a major bump. If I have an X@1.2 and there is an X@2.0, this should report X@2.0, regardless of the range I have package.json. Essentially, this should provide information to the user so they can see what packages can be upgraded to the latest, and decide if they want to change package.json to use a newer version.
The text was updated successfully, but these errors were encountered:
npm outdated
reports which versions can be updated. However, when an exact version is provided as a dependency,npm outdated
will never show that it can be updated.How it should work:
Should output:
In my mind, this should also report if a version has a major bump. If I have an
X@1.2
and there is anX@2.0
, this should reportX@2.0
, regardless of the range I have package.json. Essentially, this should provide information to the user so they can see what packages can be upgraded to the latest, and decide if they want to change package.json to use a newer version.The text was updated successfully, but these errors were encountered: