Publish npm packages

rvs selects the correct Ravenstash publication target for the command it launches.

Publish through rvs

With an authenticated rvs session, publish from the package directory without persisting a token:

rvs art select platform/releases
rvs npm publish

Inspect and publish

Preview the tarball contents before uploading:

rvs art select platform/releases
rvs npm pack --dry-run
rvs npm publish

The target determines the upload registry; no registry URL or token needs to be committed to package.json or .npmrc.

Before uploading, rvs shows the destination and package and asks for confirmation. Use rvs npm --rvs-yes publish only in a guarded automation job.

Verify the package

1. Confirm npm reports a successful publish.
2. Open the package in Ravenstash and inspect the new version.
3. Select the same repository target as described in Install npm packages.
4. Install the exact version in a clean project.

Caution

Manage mutable dist-tags from the package page or through rvs npm.

Use npm directly

To run plain npm publish, mint a short-lived publish token:

RVS_NATIVE_TOKEN=$(rvs art token mint \
  --target platform/releases \
  --format npm \
  --access publish)
export RVS_NATIVE_TOKEN

Print only the upload address or generate a complete npm publication recipe:

rvs art endpoint --target platform/releases --format npm --access publish
rvs art native config npm --target platform/releases --access publish

endpoint only prints the address. native config prints .npmrc and command examples without writing files, minting a token, or running npm.

Copy the current upload address from Ravenstash and reference the token from .npmrc:

.npmrc

//push.npm.rvsta.sh/platform/releases/:_authToken=${RVS_NATIVE_TOKEN}

Point the package at the upload registry:

package.json

{
  "publishConfig": {
    "registry": "https://push.npm.rvsta.sh/platform/releases/"
  }
}

npm publish

Do not commit a resolved token value to .npmrc. See Use tokens with package tools for expiry, access, and rotation details.