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

@digitalafarin/cms-next

v0.4.2

Published

Next.js SDK for DigitalAfarin Headless CMS + SEO

Readme

@digitalafarin/cms-next

Next.js SDK for DigitalAfarin Headless CMS + SEO.

Install

npm install @digitalafarin/cms-next

For the v0.3 release archive:

npm install ./digitalafarin-cms-next-0.3.0.tgz

Environment

DIGITALAFARIN_CMS_URL=http://localhost:8000/api/cms/v1
DIGITALAFARIN_CMS_SITE=localhost:3000

Create a client

import { createCmsClientFromEnv } from "@digitalafarin/cms-next";

export const cms = createCmsClientFromEnv({ revalidate: 60 });

App Router metadata

import { toNextMetadata } from "@digitalafarin/cms-next";
import { cms } from "@/lib/cms";

export async function generateMetadata({ params }) {
  const path = "/" + ((await params).slug ?? []).join("/") + "/";
  const page = await cms.resolve(path);
  return toNextMetadata(page);
}

resolve() can enrich the page payload with sanitized site-level SEO context. toNextMetadata() applies per-entry metadata first and falls back to site defaults such as title templates, descriptions, robots settings and default Open Graph values.

JSON-LD

import { allSchemaJsonLd } from "@digitalafarin/cms-next";

const schemas = allSchemaJsonLd(page);

The helper returns active page schemas together with the configured global Organization schema when present.

Other public helpers

The SDK also exposes typed clients/helpers for CMS resolution, site context, menus, redirects, metadata and schema rendering. See the root repository README and examples/next-site for an end-to-end consumer example.