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

@fabricorg/experiments-react

v0.1.0

Published

React bindings for Fabric Experiments: provider and hooks over @fabricorg/experiments-web.

Downloads

151

Readme

@fabricorg/experiments-react

React bindings for Fabric Experiments. A minimal provider + hooks layer over @fabricorg/experiments-web: the provider owns one browser client, and useExperiment delivers a variant and records its exposure exactly once, on delivery — assignment, bucketing, sticky storage, and exposure deduplication all stay in the web SDK.

import { ExperimentsProvider, useExperiment } from '@fabricorg/experiments-react'

function App() {
  return (
    <ExperimentsProvider
      config={{
        manifestUrl: 'https://manifest.example.com/acme/manifest',
        subjectId: currentUser.id,
        onExposure: analytics.exposure,
      }}
    >
      <CheckoutCta />
    </ExperimentsProvider>
  )
}

function CheckoutCta() {
  const { variant, payload, loading, error } = useExperiment<{ label: string }>('checkout-cta')
  if (loading) return null
  if (error) throw error
  return <button>{payload?.label ?? 'Checkout'}</button>
}

useExperimentsClient() returns the underlying experiments-web ClientApi (or null until ready) for anything the hooks don't cover.

Next.js

The provider must render inside a client component (App Router):

// app/providers.tsx
'use client'

import { ExperimentsProvider } from '@fabricorg/experiments-react'

export function Providers({ subjectId, children }: { subjectId: string; children: React.ReactNode }) {
  return (
    <ExperimentsProvider
      config={{ manifestUrl: process.env.NEXT_PUBLIC_FX_MANIFEST_URL!, subjectId }}
    >
      {children}
    </ExperimentsProvider>
  )
}

The package is SSR-safe: nothing touches window, document, or fetch during render — server-rendered markup always sees { client: null, loading: true, error: null }, and the client initializes in an effect after hydration. Server-side assignment (middleware, route handlers, RSC data loading) should use @fabricorg/experiments-node directly — see its @fabricorg/experiments-node/next adapter.

config is captured once on mount. Remount the provider (e.g. via key) to re-initialize with a different subjectId or manifestUrl.

Documentation: https://experiments.fabric.pro/docs/reference/sdk-web/

MIT