Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Prerelease versions on npmjs.org vs dist-tags #36

Open
maciej-wakula-opuscapita opened this issue Jul 14, 2021 · 0 comments
Open

Prerelease versions on npmjs.org vs dist-tags #36

maciej-wakula-opuscapita opened this issue Jul 14, 2021 · 0 comments

Comments

@maciej-wakula-opuscapita

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)

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant