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

@facet-smith/next

v0.4.0

Published

Next.js App Router integration for FacetSmith

Readme

@facet-smith/next

Next.js App Router integration for server- and client-rendered FacetSmith experiments.

Install

pnpm add @facet-smith/next

Server Component example

import {
  createNextExperiment,
  readExperimentOptions,
} from "@facet-smith/next/server";

const Hero = createNextExperiment({
  id: "server-hero",
  iteration: "launch-1",
  defaultVariant: "control",
  variants: {
    control: { revision: "1", component: Control },
    narrative: { revision: "1", component: Narrative },
  },
  allocation: { control: 0.5, narrative: 0.5 },
});

export default async function Page({ searchParams }) {
  const options = await readExperimentOptions({ searchParams });
  return Hero.render({ title: "Hello" }, options);
}

Pass an AssignmentResolver as the factory's second argument to delegate assignment. resolve() remains synchronous for the default and synchronous custom resolvers; render() awaits an async resolver before selecting a source-defined variant. See the resolver authoring guide.

For an anonymous subject, create proxy.ts:

import { createExperimentProxy } from "@facet-smith/next/proxy";

export const proxy = createExperimentProxy();

If the application already owns Proxy, compose it without duplicating its logic:

import { withExperimentSubject } from "@facet-smith/next/proxy";
import { applicationProxy } from "./src/application-proxy";

export const proxy = withExperimentSubject(applicationProxy);

The wrapped proxy receives the subject-injected request. If it forwards a custom request-header allow-list, that allow-list must retain x-experiment-subject; FacetSmith throws rather than silently assigning a different first render.

Public entry points:

  • @facet-smith/next exports shared cookie and header constants.
  • @facet-smith/next/server resolves Server Component variants and provides consolidated request options plus validated route helpers.
  • @facet-smith/next/client exports NextExperimentProvider, which includes the router-refresh bridge used after server override changes.
  • @facet-smith/next/proxy creates or composes anonymous-subject Proxy behavior.

Server switches require a cookie update and router.refresh(). Reading experiment cookies makes personalized routes request-time rendered, so do not cache personalized HTML across subjects. See the complete Next.js guide.