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

@ion-design/cms-next

v0.1.2

Published

Next.js cache, preview, rendering, and revalidation helpers for Ion CMS

Readme

@ion-design/cms-next

Next.js helpers for Ion CMS published reads, preview sessions, safe Markdown rendering, cache tags, and signed on-demand revalidation.

import { createIonNextCMS } from '@ion-design/cms-next';

export const cms = createIonNextCMS({
  projectId: process.env.ION_CMS_PROJECT_ID!,
  publicKey: process.env.ION_CMS_PUBLIC_KEY!,
  fallbackRevalidate: 3600,
});

Create the revalidation route with createIonRevalidationHandler, and use createIonPreviewExchangeHandler in a server route to exchange Ion's one-time preview code for an HTTP-only cookie. Preview credentials are never accepted by the published client.

The setup health route is deliberately small and contains no secret:

import { createIonCmsHealthHandler } from '@ion-design/cms-next';

export const GET = createIonCmsHealthHandler({
  projectId: process.env.ION_CMS_PROJECT_ID!,
});

The published wrapper attaches precise project, collection, entry, and route cache tags and uses a configurable ISR fallback. Preview uses cache: 'no-store' and a separate client:

import { readIonPreviewStateFromRequest } from '@ion-design/cms-next';

const preview = readIonPreviewStateFromRequest({
  request,
  projectId: process.env.ION_CMS_PROJECT_ID!,
});

Import IonCmsPreviewRefresh from @ion-design/cms-next/preview-refresh and add it only at the CMS page boundary. Pass it the server-provided editor origin and channel nonce; never pass the preview token to a Client Component.

IonContent renders portable Markdown and accepts an explicit component map. It rejects imports, exports, JavaScript expressions, scripts, and event handlers before rendering. Customer-owned renderers may be used instead.