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

@calmify/next

v1.4.0

Published

Receive articles from Calmify in a Next.js app: a route handler and a one-time pairing command (built on @calmify/node).

Readme

@calmify/next

Receive articles from Calmify in a Next.js (App Router) site. Built on @calmify/node, which also works with Express, React Router and other Node.js servers.

  1. npm install @calmify/next
  2. Create app/api/calmify/route.ts:
    import { createCalmifyHandler } from "@calmify/next";
    export const runtime = "nodejs";
    export const { GET, POST, DELETE } = createCalmifyHandler({
      findByKey: async (key) => /* look up a post saved with this key */ null,
      save: async (post) => { /* save to your DB/CMS, idempotent on post.idempotencyKey */ return { id: 1, url: `https://www.yoursite.com/blog/${post.slug}` }; },
      update: async (id, post) => { /* replace post `id` if its slug is post.slug, else return null */ return { id, url: `https://www.yoursite.com/blog/${post.slug}` }; },
      unpublish: async (id, slug) => { /* hide post `id` if its slug matches, else return null */ return { id, url: `https://www.yoursite.com/blog/${slug}` }; },
    });
  3. npx calmify-pair once to generate CALMIFY_API_KEY; add it to your hosting env and deploy.
  4. In Calmify: Websites → Connection → Connect, then npx calmify-pair CALM-XXXX-XXXX --endpoint https://www.yoursite.com/api/calmify.

The url you return from save (and findByKey) is the link Calmify shows for the post, so return your real article address (for example /journal/<slug> if that's your route).

Updates. When an article is edited and sent again from Calmify ("Update on site"), the receiver calls update(id, post) with the id your save returned. Replace that post (title, content, meta, cover; post.image is null when the cover was removed), store post.idempotencyKey on it so findByKey finds it on a retry, and return { id, url }. Return null when you have no post with that id and post.slug (Calmify shows "post not found"). Without update the receiver answers 422 updates_not_supported.

Unpublishing. "Unpublish from site" in Calmify sends DELETE with the post's id and slug, and the receiver calls unpublish(id, slug). Hide the post (keep it, so a later update can bring it back) and return { id, url }, or null if there's no such post. Export DELETE from your route too. Without unpublish the receiver answers 422 unpublish_not_supported.

Images inside articles. Add saveImage(image): it gets the checked bytes of each image (image.bytes, image.ext, image.alt, image.slug), stores them and returns the public URL; post.contentHtml then points there. It's called before save/update. Without it, the connection check doesn't list "images" and Calmify sends articles without their inline images.

If a post carries a cover and CALMIFY_ASSET_HOST isn't set on the server yet, the receiver refuses the post (422 asset_host_not_set) instead of saving it without its image; Calmify shows the reason. Re-running npx calmify-pair updates the keys in the env file in place.

Full guide: https://joincalmify.com/docs/connect