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

@alwatr/bobbin

v10.0.1

Published

A declarative, build-time data pipeline for fetching, validating, and caching external APIs into JSON files.

Readme

@alwatr/bobbin

A declarative, zero-dependency, build-time data pipeline for fetching, validating, and caching external APIs into JSON files.

Part of the Alwatr framework, originally extracted from @alwatr/loom to provide a standalone caching mechanism for static assets and page content during build-time.

Installation

This is a private monorepo package. In client workspaces:

"devDependencies": {
  "@alwatr/bobbin": "workspace:*"
}

API Usage

1. Defining a Source

A Source represents an external data endpoint (e.g. an API, Google Sheet, local file). It contains a name, a loader function, and an optional schema validator.

import { defineSource } from "@alwatr/bobbin";

export interface Post {
  id: number;
  title: string;
}

export const postsSource = defineSource<Post>({
  name: "posts",
  load: async () => {
    const res = await fetch("https://api.example.com/posts");
    return res.json();
  },
  schema: (data): data is Post => {
    return Array.isArray(data) && data.every((item) => typeof item.id === "number");
  },
});

2. Defining a Configuration

A configuration groups one or more data sources and defines where to write the results.

import { defineData } from "@alwatr/bobbin";
import { postsSource } from "./posts.source.js";

export const config = defineData({
  outDir: "src/data/.generated",
  sources: [postsSource],
  /**
   * Optional: minify the JSON files written to disk (removes whitespace/newlines).
   * By default, this is false and JSON outputs are pretty-printed with 2 spaces.
   */
  minify: true,
});

3. Building the Data

Trigger the data compilation script. Typically run once on checkout or when data updates.

import { buildData } from "@alwatr/bobbin";
import { config } from "./config.js";

await buildData(config);
console.log("Data successfully fetched and written to disk!");

License

MPL-2.0