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

@getsupertab/supertab-js

v3.58.0

Published

Supertab.js: Supertab browser SDK with TypeScript support

Downloads

852

Readme

Supertab.js

This package allows Supertab.js to be imported as an ES module. It includes TypeScript declarations.

npm version

Installation

Install Supertab.js from npm::

npm install @getsupertab/supertab-js

Import, load and initialize the client in your application:

import { loadSupertab } from "@getsupertab/supertab-js";

(async () => {
  const { Supertab } = await loadSupertab();
  const supertabClient = new Supertab({ clientId: "test_client.X" });
})();

loadSupertab() loads the latest compatible Supertab.js version from our CDN. It must be called in a browser environment—it won't work server-side.

Usage Example

import { loadSupertab } from "@getsupertab/supertab-js";

(async () => {
  const { Supertab } = await loadSupertab();
  const supertabClient = new Supertab({
    clientId: "client.xyz",
  });

  const { show } = await supertabClient.createPaywall({
    experienceId: "experience.xyz",
  });

  const paywallResult = await show();
  console.log(paywallResult);
})();

This example loads Supertab and creates a new Supertab.js instance using the new Supertab() constructor. Then, the createPaywall method is used to create a new paywall. The show function renders the paywall. Finally, once the user has completed or cancelled the purchase, we print the result data to the browser console.

We've put a placeholder client ID and experience ID in this example. Replace them with your actual IDs to test this code with your Supertab.js merchant account. Each experience has a corresponding client ID and experience ID. You can find them in the Supertab Business Portal under "Experiences" -> Pencil icon (edit) -> "Installation" -> "Code Snippet".

Dependencies

All dependencies in this package are listed under devDependencies in package.json. This is because:

  • The repository bundles all dependencies into the build output
  • Consumers only need the built files from e.g. dist/pkg/prod
  • No external dependencies are required at runtime
  • The reason for bundling all dependencies (even with the npm package) is to avoid dependency conflicts with the consuming app.

Note: This package does not include an engines field in package.json because Node.js is only required for building the package, not for consuming it. The published npm package contains pre-built JavaScript bundles that run in the browser, so Node.js is a build detail, not a runtime requirement.

Links