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
When I execute npm outdated on my project it shows that stack-trace is outdated: used 0.0.10 but latest is 1.0.0-pre1.
When I execute npm dist-tag ls stack-trace it shows only a single tag: latest pointing to 1.0.0-pre1.
Please, look at this page for a bit clearer description about dist tags.
Dist tags are "release channels". My guess is:
author wanted to create a pre-release version called 1.0.0-pre.1 (with a dot before 1) and tag next: npm publish --tag next
author published a version with default tag that is latest resulting in release of a stable release product 1.0.0-pre1
Please, confirm or correct me (topic is pretty new to me - I am just trying to solve the issue of npm showing outdated version where latest is pre1)
The text was updated successfully, but these errors were encountered:
When I execute
npm outdated
on my project it shows that stack-trace is outdated: used 0.0.10 but latest is 1.0.0-pre1.When I execute
npm dist-tag ls stack-trace
it shows only a single tag: latest pointing to 1.0.0-pre1.Please, look at this page for a bit clearer description about dist tags.
Dist tags are "release channels". My guess is:
1.0.0-pre.1
(with a dot before 1) and tagnext
:npm publish --tag next
latest
resulting in release of a stable release product1.0.0-pre1
Please, confirm or correct me (topic is pretty new to me - I am just trying to solve the issue of npm showing outdated version where latest is
pre1
)The text was updated successfully, but these errors were encountered: