newThe GitHub Action publishes on every pull request

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.

.github/workflows/pkg-vc.ymlGitHub Action
- name: Publish to pkg.vc
  uses: pkg-vc/publish-action@main
  with:
    organization: acme
    secret: ${{ secrets.PKG_VC_SECRET }}
review / pull #123ready
# Install the exact PR build
npm i https://pkg.vc/-/@acme/ui!123
source   feature/new-button
artifact 9f3a21c

Workflow

A package review loop that matches your code review loop.

  1. Step 1

    Publish the build

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

  2. Step 2

    Receive stable URLs

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

  3. Step 3

    Install and review

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

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

“Every pull request gets an installable package preview, without touching the public npm registry.”

Make the package installable before you make the merge permanent.

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