Skip to content

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

@maciej-wakula-opuscapita

Description

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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions