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

@osdk/seed-compiler

v0.6.0

Published

Compiles seed data files (`.mts`) into a single merged JSON output for the local ontology server to load into SQLite on startup.

Downloads

1,604

Readme

@osdk/seed-compiler

Compiles seed data files (.mts) into a single merged JSON output for the local ontology server to load into SQLite on startup.

Usage

CLI

seed-compiler \
  --metadata path/to/ontology-metadata.json \
  --seed-dir path/to/seed/ \
  --output path/to/seed-data.json

| Flag | Description | | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | --metadata | Path to the ontology-metadata.json file written by the SDK generator. Provides per-property wire types for format validation and per-object-type primary key field names. | | --seed-dir | Directory containing seed .mts files. All top-level .mts files are loaded, sorted by filename for deterministic output, and merged. | | --output | Path where the merged seed JSON is written. |

Authoring seed files

Seed files use @osdk/seed-helpers and the user's generated @ontology/sdk:

import { Product, Seller } from "@ontology/sdk";
import { createSeed } from "@osdk/seed-helpers";

export default createSeed((seed) => {
  const widget = seed.add(Product, {
    pk: "prod-001",
    title: "Widget",
    price: 100,
  });
  const alice = seed.add(Seller, {
    pk: "seller-001",
    name: "Alice",
  });

  // Link by reference — full compile-time validation on link names and target types.
  seed.link("widget-seller", widget, "sellers", alice, "products");
});

The link() method also supports a type + primary-key form for cases where keeping refs in scope is awkward:

seed.add(Product, { pk: "prod-001", title: "Widget", price: 100 });
seed.add(Seller, { pk: "seller-001", name: "Alice" });

seed.link(
  "widget-seller",
  Product,
  "prod-001",
  "sellers",
  Seller,
  "seller-001",
  "products",
);

Both forms produce identical output.

Validation

The compiler validates:

  • Object types in seed data must be defined in the ontology (via the metadata file).
  • Primary keys must be unique within an object type, across all seed files in the directory.
  • String-encoded property values must match the regex format for their wire type (timestamp, date, datetime, long, decimal).
  • Links must reference objects that were add-ed in the same seed file. Cross-file linking is not supported — the link source and target must be registered in the same createSeed(...) call.

Duplicate links (same source, target, link type) across files are deduplicated with a warning rather than an error.