Skip to content

Inverted meanings of --prerelease and --patch? #56

@chrisxvin

Description

@chrisxvin

I'm using version 13.0.4.

From help message we got:

    -p, --prerelease [<pkg,...>]       Consider prerelease versions
    -P, --patch [<pkg,...>]            Consider only up to semver-patch

But I think these two options are inverted.

I have a package(name: my-lib) with versions:

0.2.0-alpha.1
0.2.0-alpha.2
0.2.0-alpha.3
0.2.0

And I have a project with dependency:

"my-lib": "^0.2.0-alpha.1"

Then I execute:

updates -i my-lib --prerelease

I think it should tell "my-lib" can update to "0.2.0-alpha.3", but it returns "0.2.0".

If I execute:

updates -i my-lib --patch

It returns "0.2.0-alpha.3".

So, are they inverted?

PS: My test env is company's intranet, so I cannot post actual screenshots. Sorry.

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