How It Works

From code to testing in just 3 simple steps. No complex setup, no waiting time.

1. Push Code

Create a pull request and we'll detect it automatically

2. Auto Publish

We publish your package to our registry

3. Install & Test

npm install directly from the PR and test instantly

Step 1

Create Your Pull Request

Simply push your changes and create a pull request. Our GitHub integration automatically detects new PRs and starts the publishing process within seconds.

Works with any public GitHub repository
Instant PR detection and processing
Zero configuration or setup required
GitHub Repository
Open
feat: Add new button component #123

Add reusable button component with variants and accessibility features

+47 additions -12 deletions 3 files changed
pkg.vc bot will comment shortly...
Publishing Pipeline
Processing
Build completed
12.4s
Tests passed
8.2s
Package validated
1.8s
Publishing to registry
0.9s
✅ Package published successfully!
📦 my-package!pr-123
Step 2

Automatic Publishing

Your existing CI builds the package. Once built, we automatically publish it to our registry with a unique PR identifier—no manual intervention required.

Leverages your existing CI/CD pipeline
Automatic validation and testing
Global CDN distribution
Step 3

Install & Test Instantly

Install the package directly from the pull request using your favorite package manager. Test the changes in your project before the PR gets merged.

Works with npm, yarn, pnpm, and bun
Share test versions with your team
Easy cleanup and management
Terminal
$ # Install from PR #123
$ npm install https://pkg.vc/-/my-package!pr-123
+ my-package@pr-123
added 1 package in 1.8s
$ # Test the new features
$ npm run dev
✅ All tests passing!
✨ New button component works perfectly
$ # Also works with other package managers
$ bun add https://pkg.vc/-/my-package!pr-123

Why This Changes Everything

Compare the traditional package testing workflow to our streamlined approach

Traditional Workflow

Manual npm publish commands

Time-consuming manual publishing process

Complex version management

Risk of version conflicts and confusion

Slow feedback cycles

Wait hours for merge before testing integration

Registry cleanup nightmare

Manual deletion of test versions

⏱️ Average: 2-3 hours per test cycle

pkg.vc Way

Fully automatic publishing

Clean main registry, zero manual intervention

Smart PR-based versioning

Each PR gets a unique, clean identifier

Instant feedback loops

Test immediately after pushing changes

Automatic cleanup

Packages expire automatically, no maintenance

⚡ Average: Under 2 minutes per test

Ready to Ship Faster?

Start testing packages instantly with pkg.vc

No credit card required
Free forever plan
Setup in under 2 minutes