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

mnfst-types

v0.1.15

Published

Generate TypeScript types for a Manifest project from manifest.json and sample data

Readme

mnfst-types

Generate a manifest.d.ts file for a Manifest project so editors and AI coding assistants understand the shape of $x.<source>, $route, $modify, and the other Manifest magic globals.

Usage

From the root of a Manifest project (next to manifest.json):

npx mnfst-types

This writes manifest.d.ts in the current directory. Re-run it whenever you add or change a data source in manifest.json.

Options

--manifest <path>   Path to manifest.json (default: ./manifest.json)
--out <path>        Output .d.ts path (default: ./manifest.d.ts)
--init              Also write a baseline jsconfig.json (only if missing)
--ci                Also write .github/workflows/types.yml (only if missing)
--check             Exit 1 if the output is out of date; write nothing
--tsc               Type-check the scripts the page loads (paths from the import map)
-h, --help          Show usage

Type checks without a build

npx mnfst-types --tsc

Type-checks the scripts index.html and the manifest's component files load (and everything they import), plus the project's .d.ts files. The config is built on every run: paths come from the page's import map, so adding an alias never needs a config change. No folder layout is assumed. A project jsconfig.json or tsconfig.json is extended — its own options and paths win.

--init writes a jsconfig.json so editors show the same errors as you type; run it again after changing the import map to add new aliases to it. --ci adds a GitHub Actions workflow running --check and --tsc on every push. See https://manifestx.dev/docs/framework/getting-started/type-checks.

How it works

  1. Reads manifest.json and walks each entry under data.
  2. For local CSV / JSON / YAML sources, samples the first ~50 rows to infer field types.
  3. For Appwrite-table sources, rows accept any field until the project declares their type in ManifestRows.
  4. For Appwrite-bucket sources, types the source as ManifestBucketSource.
  5. Combines the inferred row types with the static ambient declarations and writes a single manifest.d.ts.

The generated file's static portion (magic globals, query operators, source-state flags) is fixed; only the section between // AUGMENTATION:start and // AUGMENTATION:end is regenerated on subsequent runs.

Companion: manifest.json JSON Schema

For autocomplete and validation in manifest.json itself, add a $schema reference at the top of the file:

{
    "$schema": "https://manifestx.dev/manifest.schema.json",
    "name": "My Project",
    "data": { ... }
}

VS Code and most JSON-aware editors will fetch and apply the schema automatically.