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

@cuped-io/flame

v0.5.0

Published

Client-side A/B testing SDK for cuped.io

Readme

@cuped-io/flame

npm License: MIT

Client-side A/B testing SDK for cuped.io.

Drop a <script> tag on your page and define variants in the cuped.io dashboard, or import the SDK and drive variants from your own code.

Install

pnpm add @cuped-io/flame
# or
npm install @cuped-io/flame

For React, see @cuped-io/flame-react. For Next.js zero-flash SSR, also see @cuped-io/flame-edge.

You'll need a DSN — get one at cuped.io under Settings → Install snippet.

Usage

Script tag (no-code DOM mutations)

Pin to a version and guard it with Subresource Integritycrossorigin is required for SRI on the cross-origin script:

<script
  src="https://cdn.cuped.io/[email protected]"
  integrity="sha384-hFM7xfw0tzMU7yK4TR8fA6Y2DNtbFSlR2CuE8CIESzD1QeYoHD0e4NJJdVccYeCl"
  crossorigin="anonymous"
  data-dsn="https://[email protected]"
></script>

The SDK auto-initializes from the data-dsn attribute, fetches active experiments, applies variant DOM changes, and tracks events. Define the changes per variant in the cuped.io dashboard.

The SRI hash for every published version is listed in cdn.cuped.io/flame.sri.json (a versions map plus a latest pointer). Pinned [email protected] URLs are write-once and never removed, so a pin keeps resolving byte-for-byte across all later releases and can always be rolled back to. The unversioned https://cdn.cuped.io/flame.js is a floating "latest" that always serves the newest release — convenient, but it can't be SRI-pinned (its bytes change on every release) and gives up rollback safety.

Programmatic

import { flame } from '@cuped-io/flame';

await flame.init({ dsn: 'https://[email protected]' });

if (flame.isInVariant('hero-cta', 'treatment')) {
  // ...
}

// Fire any custom event. Define a matching goal once at the project
// level on cuped.io (Project → Goals → Custom event); any experiment
// in the project can then attach it as primary or secondary.
flame.track('vote_cast', { game_id: 'g42', option: 'controller' });

The SDK POSTs every event to POST /{api_key}/events as the array envelope { "events": [ … ] } (a single event is an array of one).

Public API

// Lifecycle
flame.init({ dsn, prehydrated? })

// Events — one verb. Use track('pageview') on SPA navigation and
// track('conversion', …) for conversions.
flame.track(eventType, metadata?)

// Identity
flame.identify(userId)
flame.clearIdentity()
flame.getUserId()
flame.getIdentity()

// Experiments
flame.getVariant(experimentId)
flame.getAssignedVariantInfo(experimentId)
flame.isInVariant(experimentId, variantOrName)
flame.isInitialized()
flame.reset()

Variant change types

When using the script-tag flow, variants can apply 8 change types to the DOM via CSS selectors: text, html, attribute, class, style, css, visibility, redirect. Configured in the cuped.io dashboard.

Documentation

License

MIT