Skip to content

Instantly share code, notes, and snippets.

@adcreare

adcreare/npm-beta-publish.md

Last active March 26, 2025 16:15
Show Gist options
  • Save adcreare/00a10f389841dd4c97197608c9b33a7f to your computer and use it in GitHub Desktop.
Save adcreare/00a10f389841dd4c97197608c9b33a7f to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. adcreare revised this gist Jul 26, 2019. 1 changed file with 3 additions and 3 deletions.
    6 changes: 3 additions & 3 deletions npm-beta-publish.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,12 +1,12 @@
    Steps to publish a npm package to beta that won't be available via latest and won't auto install on ncu updates etc

    1. Ensure any compile is run `yarn dist` etc
    1. Ensure any compile is run `npm run dist` etc
    2. Modify version in package.json to the following format (match with existing verion numbers etc) `"version": "0.1.120-beta.1"` where beta.x is the number of those betas
    3. Publish to npm `npm publish --tag beta`

    There are two options for install:
    * Always install beta with `yarn add packagename@beta`
    * Install specific version with `yarn add [email protected]`
    * Always install beta with `npm install packagename@beta`
    * Install specific version with `npm install [email protected]`

    How to fix latest if you publish a beta without --tag beta (if will default to latest)
    run: `npm dist-tags add @COMPANY/[email protected] latest --otp=123456`where 1.0.3 is the version that should be latest --otp= is required
  2. adcreare revised this gist May 20, 2018. 1 changed file with 4 additions and 1 deletion.
    5 changes: 4 additions & 1 deletion npm-beta-publish.md
    View file
    Original file line number Diff line number Diff line change
    @@ -6,4 +6,7 @@ Steps to publish a npm package to beta that won't be available via latest and wo

    There are two options for install:
    * Always install beta with `yarn add packagename@beta`
    * Install specific version with `yarn add [email protected]`
    * Install specific version with `yarn add [email protected]`

    How to fix latest if you publish a beta without --tag beta (if will default to latest)
    run: `npm dist-tags add @COMPANY/[email protected] latest --otp=123456`where 1.0.3 is the version that should be latest --otp= is required
  3. adcreare created this gist Mar 28, 2018.
    9 changes: 9 additions & 0 deletions npm-beta-publish.md
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,9 @@
    Steps to publish a npm package to beta that won't be available via latest and won't auto install on ncu updates etc

    1. Ensure any compile is run `yarn dist` etc
    2. Modify version in package.json to the following format (match with existing verion numbers etc) `"version": "0.1.120-beta.1"` where beta.x is the number of those betas
    3. Publish to npm `npm publish --tag beta`

    There are two options for install:
    * Always install beta with `yarn add packagename@beta`
    * Install specific version with `yarn add [email protected]`