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

@yamblog/core

v1.0.1

Published

Framework-agnostic markdown blog engine

Downloads

137

Readme

@yamblog/core

Framework-agnostic markdown blog engine. File-based, type-safe, zero-config.

Install

npm install @yamblog/core

Quick start

import { createBlog } from '@yamblog/core';

const blog = createBlog({ contentDir: './content/posts' });

const posts    = await blog.getPosts();
const post     = await blog.getPostBySlug('hello-world');
const results  = await blog.search('typescript');
const related  = await blog.getRelatedPosts('hello-world');
const adjacent = await blog.getAdjacentPosts('hello-world');
const rss      = await blog.generateRss({ siteUrl, title, description });
const sitemap  = await blog.generateSitemap({ siteUrl });
const index    = await blog.generateSearchIndex(); // lightweight JSON for client search

Content validation

Use the same parser and schema checks in CI, a build step, or a Git hook:

import { validateContent } from '@yamblog/core';

await validateContent({
  contentDir: './content/posts',
});

If you already create a blog instance, you can validate through that too:

import { createBlog } from '@yamblog/core';

const blog = createBlog({ contentDir: './content/posts' });
await blog.validateContent();

Both forms throw when:

  • the content directory does not exist
  • a markdown file has invalid frontmatter
  • two files resolve to the same slug

Frontmatter schema

---
title: "Post Title"
slug: "post-title"
date: "2026-01-15"
author: "Author Name"
tags: ["tag1", "tag2"]
excerpt: "One or two sentence summary."
published: true
---

Computed fields added automatically: id ("blog-{slug}"), readingTime, content.

Custom schema

import { createBlog } from '@yamblog/core';
import { z } from 'zod';

const blog = createBlog({
  contentDir: './content/posts',
  schema: z.object({
    title: z.string(),
    date: z.coerce.date(),
    category: z.string(),
    tags: z.array(z.string()).default([]),
    draft: z.boolean().default(false),
  }),
});

API

| Method | Returns | |--------|---------| | getPosts() | All published posts, sorted newest first | | getPostBySlug(slug) | Single post (throws if not found) | | getPostsByCategory(cat) | Posts filtered by category | | getPostsByTag(tag) | Posts filtered by tag | | getFeaturedPosts() | Posts where featured: true | | getCategories() | Unique category strings | | getTags() | Unique tag strings | | search(query) | Full-text search (title › excerpt › content) | | getAdjacentPosts(slug) | { prev, next } for navigation | | getRelatedPosts(slug) | Related posts by tags/category | | generateRss(options) | RSS 2.0 XML string | | generateSitemap(options) | Sitemap XML string | | generateSearchIndex() | Lightweight JSON array for client-side search |

Stable blog ID

Every post exposes post.id = "blog-{slug}" — a stable foreign key you can wire into comments, analytics, or related-content services without worrying about it changing.