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

@ingram-tech/nk-blog

v0.1.1

Published

File-based blog foundation for Next.js sites: frontmatter schema, build-time reader, limited-MDX rendering, a typed component contract with unstyled defaults, GitHub read/publish, and RSS.

Downloads

272

Readme

@ingram-tech/nk-blog

File-based blogs for Next.js sites: one frontmatter contract, a build-time reader, .md/limited-.mdx rendering, a typed component vocabulary with unstyled defaults, GitHub read/publish for automated publishers, and RSS.

The files are the index. Posts are content/blog/<slug>.md (or .mdx, or <slug>/index.mdx folders) with YAML frontmatter. There is no generated posts.json, no metadata-extraction script, and nothing to drift.

Entry points

| Import | Contents | Where | |---|---|---| | @ingram-tech/nk-blog | frontmatter schema, types, vocabulary manifest, reading time, dates, JSON-LD bridge | anywhere | | @ingram-tech/nk-blog/server | createBlog, fsSource, githubSource, publishPost, serializePost, generateRss, keys | server only | | @ingram-tech/nk-blog/render | PostBody, MarkdownBody, MdxBody, remarkLimitedMdx, validateLimitedMdx | server components | | @ingram-tech/nk-blog/unstyled | behavior-correct, zero-styling vocabulary defaults | server components |

Site setup

// src/lib/blog.ts
import { createBlog, fsSource } from "@ingram-tech/nk-blog/server";

export const blog = createBlog({
	source: fsSource("content/blog"),
	defaultAuthor: "Example Team",
	drafts: process.env.NODE_ENV !== "production",
});
// src/lib/blog-components.tsx — the site's entire vocabulary obligation
import { defineBlogComponents } from "@ingram-tech/nk-blog";
import { unstyled } from "@ingram-tech/nk-blog/unstyled";

export const blogComponents = defineBlogComponents({
	...unstyled,
	// Callout: BrandCallout, — replace wholesale where the brand cares
});
// src/app/blog/[slug]/page.tsx — full SSG, no runtime fs
import { PostBody } from "@ingram-tech/nk-blog/render";
import { blog } from "@/lib/blog";
import { blogComponents } from "@/lib/blog-components";
import { mdxElements } from "@/mdx-components"; // the site's own element map

export const dynamicParams = false;
export async function generateStaticParams() {
	return (await blog.slugs()).map((slug) => ({ slug }));
}

export default async function Post({ params }: PageProps<"/blog/[slug]">) {
	const { slug } = await params;
	const post = await blog.post(slug);
	if (!post) notFound();
	return <PostBody post={post} components={blogComponents} elements={mdxElements} />;
}

The rules that keep this portable

  • Vocabulary, not imports. A Tier-1 post references <Callout>, <Figure>, <YouTube>, <Tweet>, <NewsletterSubscribe> by bare name and nothing else. render enforces this in the AST (remarkLimitedMdx): no ESM, no {…} expressions, literal props only. Automated publishers emit .md (pure data) and validate .mdx with validateLimitedMdx before committing.
  • Tier-2 (bespoke) posts are folders with human-reviewed components.tsx, passed via bespoke — which relaxes enforcement, because a human merged it.
  • No pixels in this package. The unstyled defaults carry semantics and behavior only and accept no visual props beyond className. Want variation? Replace the component in your registry — never add props here.
  • Build-time only. fsSource runs under generateStaticParams / dynamicParams = false; serverless functions must not read post files at request time (output tracing won't include them).