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

@matthewp/cook-loader

v0.1.8

Published

Astro Content Layer loader for Cooklang (.cook) recipe files.

Downloads

229

Readme

@matthewp/cook-loader

An Astro Content Layer loader for Cooklang .cook recipe files.

Install

npm install @matthewp/cook-loader

Peer dependencies: astro (≥4.14, where the Content Layer landed) and zod.

Usage

// src/content.config.ts
import { defineCollection, z } from 'astro:content';
import { cooklang, recipeSchema } from '@matthewp/cook-loader';

const recipes = defineCollection({
  loader: cooklang({ base: 'src/content/recipes' }),
  schema: recipeSchema({
    metadata: z.object({
      title: z.string(),
      author: z.string().optional(),
      servings: z.coerce.number().optional(),
      emoji: z.string().optional(),
    }),
  }),
});

export const collections = { recipes };

Then in a page:

---
import { getCollection } from 'astro:content';
const recipes = await getCollection('recipes');
---
{recipes.map((r) => (
  <article>
    <h1>{r.data.metadata.title}</h1>
    <ul>
      {r.data.ingredients.map((i) => <li>{i.quantity} {i.units} {i.name}</li>)}
    </ul>
    {r.data.steps.map((step) => (
      <p>{step.map((t) => t.type === 'text' ? t.value : t.name)}</p>
    ))}
  </article>
))}

Data shape

Each entry's data is:

{
  metadata: { /* your `>> key: value` lines, typed via your schema */ },
  ingredients: Array<{ name, quantity, units }>,
  cookware: Array<{ name, quantity }>,
  steps: Array<Array<StepToken>>,
}

Step tokens are a discriminated union of text, ingredient, cookware, and timer. Inline ingredient/cookware tokens carry an index field that points back to their position in the ingredients/cookware arrays — useful for rendering inline mentions as anchor links to ingredient list items.

Schema extension

recipeSchema() owns the structural shape — ingredients, cookware, and the tokenised steps. The only extension point is metadata. Pass any Zod object for it; coerce types if you want:

recipeSchema({
  metadata: z.object({
    title: z.string(),
    servings: z.coerce.number(),
    tags: z.string().transform((s) => s.split(',').map((t) => t.trim())).optional(),
  }),
});

If you omit the metadata option you get z.record(z.string(), z.string()).

Options

cooklang({
  base: 'src/content/recipes',  // directory to search (relative to project root)
  pattern: '**/*.cook',         // glob pattern relative to base
  generateId: (relPath) => relPath.replace(/\.cook$/, ''),  // custom id mapping
});

License

BSD-3-Clause