npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@koryla/next

v0.1.1

Published

A/B testing for Next.js with zero flicker. Runs on the Vercel Edge Network.

Readme

@koryla/next

A/B testing for Next.js with zero flicker. Runs on the Vercel Edge Network.

Installation

npm install @koryla/next

Setup

1. Add environment variables

# .env.local
KORYLA_API_KEY=sk_live_...   # generated in Koryla → Settings → API Keys
KORYLA_API_URL=https://your-koryla-app.vercel.app

2. Create middleware.ts

// middleware.ts  (project root, next to package.json)
import { korylaMiddleware } from '@koryla/next'

export default korylaMiddleware({
  apiKey: process.env.KORYLA_API_KEY!,
  apiUrl: process.env.KORYLA_API_URL!,
})

// Only run on the pages you're testing — keeps other routes fast
export const config = {
  matcher: ['/', '/pricing', '/landing'],
}

3. Create your variant pages

The middleware rewrites the URL server-side, so the variant page must exist in your app:

app/
  page.tsx           ← control  (base_url: https://acme.com/)
  variant-b/
    page.tsx         ← variant  (target_url: https://acme.com/variant-b)

4. Create an experiment in Koryla

Go to your Koryla dashboard → New experiment:

| Field | Value | |-------|-------| | Base URL | https://acme.com/ | | Variant A — Control | https://acme.com/ · 50% | | Variant B | https://acme.com/variant-b · 50% | | Conversion URL | https://acme.com/thank-you |

Set it to Active and you're done.

How it works

User visits /
     │
     ▼
Next.js middleware (runs at Vercel edge, before rendering)
     │
     ├── calls Koryla API once every 60s to get experiment config
     ├── reads sp_<experimentId> cookie
     │     ├── cookie present → use existing variant (sticky)
     │     └── no cookie → assign variant by traffic weight
     │
     ├── rewrites request to /variant-b (server-side, no redirect)
     └── sets cookie for 30 days
     │
     ▼
Next.js renders /variant-b
Browser receives variant B HTML — never sees the rewrite

Why this is better than VWO / Optimizely

| | VWO / Optimizely | @koryla/next | |--|--|--| | When variant is decided | In the browser, after JS loads | At the edge, before any HTML | | Flicker | Yes (page hides while swapping) | No | | Extra JS | ~80–150 KB | 0 KB | | Blockable by ad blockers | Yes | No | | Works without JS | No | Yes |