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

@schemat/parser-mongoose

v0.2.1

Published

Mongoose parser for Schemat (Mongoose schemas -> IR, static AST).

Readme

@schemat/parser-mongoose

Mongoose parser for Schemat: turns Mongoose schema definitions into the canonical Schemat IR by statically parsing the source (via ts-morph) — it never connects to MongoDB, imports your app, or runs your code.

MongoDB is schemaless at the database level. This parser reads the application-level Mongoose schema (a logical model in code), not a physical database schema. "Tables" are Mongoose models/collections; "relations" are derived from ref conventions, not enforced foreign keys.

Install

npm i @schemat/parser-mongoose

Usage

import { mongooseParser } from "@schemat/parser-mongoose";

const ir = await mongooseParser.parse({ projectPath: "." });

// Or point at specific model files:
const ir2 = await mongooseParser.parse({ projectPath: ".", files: ["src/models/user.ts"] });

mongooseParser implements the SchemaParser interface (detect + parse) from @schemat/core and returns an IRSchema.

Detection

Detects a Mongoose project when any of these hold:

  • mongoose is a dependency in package.json, or
  • a source file contains new Schema( / new mongoose.Schema(, or
  • a models/* file imports mongoose.

What it maps

  • new Schema({...}) + model('Name', schema) → tables (named after the model; falls back to the schema variable name when no model() call links it)
  • Every model gets an implicit _id ObjectId primary key (matching Mongoose)
  • Fields (shorthand age: Number and options-object { type, required, unique, default, enum, ref }) → columns; required → not-null, unique, default
  • enum: ['a','b'] on a String field → an enum named <Model>_<field>
  • { type: ObjectId, ref: 'Other' } → a one-to-many relation (fromColumns: [field], toColumns: ['_id']); an array of refs ([{ type: ObjectId, ref }]) → many-to-many

Limitations (v1)

  • Nested subdocuments (inline object fields like address: { city: String }) are collapsed to a single Object column — not recursed into separate tables.
  • Arrays of primitives collapse to an Array column.
  • ref targets are matched by model name; a ref to a model not present in the parsed files still emits the edge (Mongo doesn't enforce FKs).

License

MIT © Ali Reza Hamid