npm previews / before merge

Run the package.
Then review the PR.

Publish an npm package build from your pull request and give reviewers an installable, immutable URL—without pushing a preview version to npm.

review / pull #123● BUILD READY
# Install the exact PR build
npm i https://pkg.vc/-/@acme/ui!123
# Use it in the consuming app
npm test
sourcefeature/new-buttonartifact9f3a21cstatusinstallable

01 / workflow

A package review loop that matches your code review loop.

  1. 01

    Publish the build

    Use the CLI for a one-off publish or the GitHub Action on every pull request.

  2. 02

    Receive stable URLs

    pkg.vc returns addresses for the pull request, branch, and exact commit.

  3. 03

    Install and review

    Paste the URL into npm, yarn, or pnpm and test the actual package in a consuming app.

02 / addressing

One build. Three useful addresses.

Choose a moving reference for ongoing review or pin the precise artifact you approved.

pull requestpkg.vc/-/@acme/ui!123
branchpkg.vc/-/@acme/ui~feature/nav
commitpkg.vc/-/@acme/ui@9f3a21c

Why pkg.vc

Proof before release.

Keep preview builds off the public npm registry
Give every reviewer the same immutable artifact
Automate publication with GitHub Actions
Control private package access with API keys

Used in production package workflows at

Appwrite

Built to support thousands of developers publishing and testing package previews.

pkg.vc scale

Start free

Publish first. Upgrade when your workflow needs more.

Public modules are free to start. Pro adds private modules and team workflows.

Ready for review?

Make the package installable before you make the merge permanent.

Publish your first package →