How to generate NPM release candidate version

前端 未结 4 1210
时光取名叫无心
时光取名叫无心 2020-12-09 19:06

Say I want to generate a pre-release NPM version.

Originally I have this:

   \"version\": \"0.0.1\"

I tried:

npm ve         


        
相关标签:
4条回答
  • 2020-12-09 19:46

    You can use:

    npm version prerelease --preid=rc
    

    Result: v1.0.0-rc.0

    0 讨论(0)
  • 2020-12-09 19:47

    UPDATE

    As of npm 6.3.0-next.0 you can now use --preid when tagging pre-releases with version.

    npm version prerelease --preid=next
    

    NPM Link: https://docs.npmjs.com/cli/version


    Original answer

    Sadly (and a little bit ironic) npm does not fully support all the features of semver!

    What you need is a feature called pre-id, found in the semver spec #9. I have submitted a PR to npm to fix it but it was rejected. https://github.com/npm/npm/pull/13794

    preids basically allow you to specify an id for a prerelease, for example:

    1.0.0-alpha or 1.0.0-alpha.1
    

    Forrest rejected this proposal in a comment writing this:

    After some further consideration, and discussion within the team, I've decided that this isn't a change the CLI team is going to land. Working with prerelease versions is tricky, and this feature is enough of an edge case that I think it increases, rather than decreases, the number of opportunities for prerelease versions to be a footgun.

    My concern about footguns is connected to the decision, in semver@^4, to make prerelease versions fall outside the range matching for ~ and ^. Were semver's behavior to change, it might make more sense to have a way to opt into (and then increment within) a given prerelease identifier. After watching the travails of the React community in using prerelease versions with peerDependencies and other interrelated suites of packages, it's pretty clear that the current behavior of semver with respect to prerelease versions is of pretty limited usefulness. That means there's a substantial possibility that that behavior may change.

    As it stands, though, I think users who want to use prerelease versions are better off using third-party tools like npmversion, or build scripts that use npm version "x.y.z-prealpha.2" (or whatever suits your use case) instead. Thanks for your time, and my apologies for the delay!

    As he recommends, to get this working you should be using a tool that does support full semver versioning. I presonally recommend semver package, found in the npm documentation itself here https://docs.npmjs.com/misc/semver

    0 讨论(0)
  • 2020-12-09 19:47

    Looks like:

    npm version prerelease

    is basically what I am looking for, but this doesn't add alpha/beta/rc to the version, it just does this x.y.z-n.

    0 讨论(0)
  • 2020-12-09 19:50

    npm version prerelease will generate 0.0.0-x version

    0 讨论(0)
提交回复
热议问题