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

stepskit

v0.1.1

Published

StepsKit loader — product tours, tooltips, surveys and announcements with a typed API.

Readme

stepskit

The official npm package for StepsKit — product tours, tooltips, surveys and announcements for your web app.

This is a typed loader (~1 KB), not the whole runtime. It installs a pre-load call queue, injects the evergreen StepsKit runtime from cdn.stepskit.com, and gives you a fully typed API. The npm version versions the loader — the tour engine itself streams from the CDN and is always current, so you never need to bump this package to pick up engine fixes.

Quickstart

npm install stepskit
import stepskit from "stepskit";

stepskit.init("YOUR_API_KEY");

Call init() once at your app's entry point. It is SSR-safe (a no-op on the server) and idempotent (calling it twice injects nothing).

Migrating from the <script> snippet? Remove the snippet when you add the package — the snippet injects unconditionally, and two loaders mean two embed instances.

React / Next.js

import { StepsKit } from "stepskit/react";

// Next.js App Router: app/layout.tsx (it's already a client-safe component)
// Vite/CRA: your top-level <App />
<StepsKit
  apiKey="YOUR_API_KEY"
  user={{ id: user.id, email: user.email, plan: user.plan }}
/>;

The component renders nothing, loads StepsKit once (StrictMode-safe), and identifies the user when the user prop appears or its values change — passing a new object with the same values does not re-identify.

Identify your users

stepskit.identify({ id: "user_123", email: "[email protected]", plan: "pro" });

Without an id, show-once frequency capping and audience targeting silently do nothing — every visitor is anonymous. Call identify once, when your auth state resolves. Calls made before the runtime finishes loading (or even before init()) are queued and replayed in order, so identity is always set before the first tours fetch.

API

The full API is documented at stepskit.com/docs/api. Everything on window.stepskit is on the stepskit import, fully typed:

| Method | Pre-load behavior | | --- | --- | | identify(user) | queued | | setUserAttributes(attrs, opts?) | queued | | playTour(id) / stopTour() / refresh() | queued | | on(event, fn) / off(event, fn) | queued | | dismissAnnouncement(id) / destroy() / track() | queued | | isPlaying() | false | | getTours() | [] | | getUserAttributes() | undefined | | validateEnvironment() | undefined |

Options

stepskit.init("YOUR_API_KEY", {
  apiUrl: "https://stepskit.your-domain.com", // self-hosted / local API origin
  debug: true, // [StepsKit] info logs
  user: { id: "user_123" }, // identify as part of init
  nonce: cspNonce, // CSP nonce for the injected <script>
});

If your Content-Security-Policy restricts script-src, allow https://cdn.stepskit.com (and https://stepskit.com for connect-src).

Plain HTML / CMS / GTM

No build step? Use the copy-paste <script> snippet from your StepsKit dashboard instead — see stepskit.com/docs/install/js.

CommonJS

The package ships both ESM and CJS. In CommonJS, use the named export:

const { stepskit } = require("stepskit");