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/react

v0.1.4

Published

React Server Component SDK for Koryla A/B testing. Zero client-side JavaScript — variants are resolved on the server before the page renders.

Downloads

43

Readme

@koryla/react

React Server Component SDK for Koryla A/B testing. Zero client-side JavaScript — variants are resolved on the server before the page renders.

Installation

npm install @koryla/react

Setup

1. Add environment variables

# .env.local
KORYLA_API_KEY=sk_live_...
KORYLA_API_URL=https://koryla.com

2. Create a Koryla client

Instantiate once — it holds the 60s config cache:

// lib/koryla.ts
import { createKoryla } from '@koryla/react'

export const koryla = createKoryla({
  apiKey: process.env.KORYLA_API_KEY!,
  apiUrl: process.env.KORYLA_API_URL!,
})

3. Use in your page or component

// app/page.tsx (Next.js App Router)
import { headers } from 'next/headers'
import { koryla } from '@/lib/koryla'
import { Experiment, Variant } from '@koryla/react'

export default async function Page() {
  const result = await koryla.getVariant(
    'your-experiment-id',           // from Koryla dashboard
    headers().get('cookie') ?? '',  // sticky sessions via cookie
  )

  return (
    <main>
      <Experiment variantId={result?.variantId ?? ''}>
        <Variant id="control">
          <h1>Original headline</h1>
        </Variant>
        <Variant id="variant-b">
          <h1>New headline that converts better</h1>
        </Variant>
      </Experiment>
    </main>
  )
}

4. Persist the variant cookie

On new assignments the visitor's variant isn't sticky yet. Set the cookie in a Next.js middleware:

// middleware.ts
import { koryla } from '@/lib/koryla'
import { NextResponse } from 'next/server'

export async function middleware(request) {
  const result = await koryla.getVariant(
    'your-experiment-id',
    request.headers.get('cookie') ?? '',
  )
  const response = NextResponse.next()
  if (result?.isNewAssignment) {
    response.cookies.set(result.cookieName, result.variantId, {
      maxAge: 60 * 60 * 24 * 30,
      sameSite: 'lax',
      path: '/',
    })
  }
  return response
}

How it works

User visits /
     │
     ▼
Next.js renders Page server component
     │
     ├── koryla.getVariant() reads config (cached 60s)
     ├── reads koryla_sid cookie
     │     ├── cookie present → use existing variant (sticky)
     │     └── no cookie → assign variant by traffic weight
     │
     └── <Experiment> renders only the matching <Variant>
     │
     ▼
Browser receives HTML with the correct variant already rendered
No JS, no swap, no flicker

API

createKoryla(options)

| Option | Type | Description | |--------|------|-------------| | apiKey | string | Your sk_live_... key from Settings → API Keys | | apiUrl | string | https://koryla.com | | cacheTtl | number | Config cache TTL in ms. Default: 60000 |

Returns { getVariant }.

koryla.getVariant(experimentId, cookieHeader)

Returns Promise<VariantResult | null>. null means the experiment wasn't found or is inactive.

interface VariantResult {
  experiment: Experiment
  variant: Variant         // the assigned variant object
  variantId: string        // e.g. "abc-123"
  isNewAssignment: boolean
  cookieName: string       // e.g. "ky_exp-id"
}

<Experiment variantId={...}>

Renders only the <Variant> child whose id matches variantId. Falls back to the first child if no match.

<Variant id="...">

Marker component. Wrap content inside <Experiment>.

Why this is better than VWO / Optimizely

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