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

@scadable/react

v0.1.0

Published

Render your always-current SCADABLE privacy policy or terms of use in any React app (Vite, CRA, Remix, Gatsby).

Readme

@scadable/react

Render your always-current SCADABLE privacy policy or terms of use in any React app (Vite, Create React App, Remix, Gatsby, even a Next.js client component). You publish the document once in the SCADABLE app; this component shows whatever version is currently published, pulled live in the browser, so updating it never means a redeploy on your side.

Install

npm install @scadable/react

Use

Give it one thing, your scope's public token, and you are done.

import { PrivacyPolicy } from '@scadable/react';

export default function PrivacyPage() {
  return (
    <main>
      <PrivacyPolicy token="YOUR_PUBLIC_TOKEN" />
    </main>
  );
}

Terms of use is the same, with its own wrapper:

import { TermsOfUse } from '@scadable/react';

export default function TermsPage() {
  return <TermsOfUse token="YOUR_PUBLIC_TOKEN" />;
}

Or use the generic component and pick the document with docType:

import { ScadablePolicy } from '@scadable/react';

export default function Page() {
  return <ScadablePolicy token="YOUR_PUBLIC_TOKEN" docType="terms_of_use" />;
}

Get YOUR_PUBLIC_TOKEN from the SCADABLE app after you publish a document.

Options

| Prop | Type | Default | Notes | | --- | --- | --- | --- | | token | string | required | Your scope's public token. | | docType | string | "privacy_policy" | Which document to render (ScadablePolicy only). | | className | string | none | Class on the wrapper element. | | showVersion | boolean | false | Show a "Version N, last updated ..." line. | | baseUrl | string | https://api.scadable.com | Override the API base. | | initialHtml | string | none | Pre-fetched HTML for SSR hosts. See below. |

Always live

The document is fetched in the browser when the component mounts and injected, so any edit you publish in SCADABLE shows up on the next page load with no redeploy on your side. The returned HTML is a self-styled fragment that inherits your page's text color and already includes the "by scadable.com" backlink. If the browser fetch is blocked (a strict Content-Security-Policy) or offline, the component keeps whatever is already shown, so the page is never blank.

SSR hosts (Remix, Gatsby, Next client)

If your host fetches the document itself during server render or build (for SEO and to avoid a first-paint flash), pass that HTML as initialHtml. The component renders it immediately, then swaps in the live copy on mount.

import { fetchPolicy } from '@scadable/core';
import { PrivacyPolicy } from '@scadable/react';

// In your loader / getStaticProps / server component:
const policy = await fetchPolicy('YOUR_PUBLIC_TOKEN');

// In the component tree:
<PrivacyPolicy token="YOUR_PUBLIC_TOKEN" initialHtml={policy.html} />;

This is optional. With no initialHtml the component works as a pure client-only SPA widget and shows a small loading line until the first fetch lands.

Notes

  • This package only talks to the public SCADABLE API. It stores no secrets.
  • The rendered HTML is your own published document content from the SCADABLE API.