Skip to content

Alpha versions should not be published as latest on npm #225

Description

@marvinroger

Describe the bug

Currently, v6.0.0-alpha.3 is published on npm under the latest tag. I think doing npm i @faker-js/faker should install the latest stable, not the latest alpha. Therefore, I'd suggest publishing v6.0.0-alpha.3 under the alpha tag (npm publish --tag alpha), and publishing a v5.5.4 (exact content of v5.5.3) under the latest tag.

Reproduction

Run npm i @faker-js/faker, it installs the latest alpha instead of the latest stable.

Additional Info

Note that maybe there's a valid reason to do so, I might be missing context here, since the library situation was/is quite complicated. 😉

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions