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

schematica

v1.1.19

Published

General Purpose library for working with Json, includes validation and parsing utils, currently WIP, array support coming soon

Downloads

68

Readme

Features

  • Schema validation
  • Serialization
  • Parsing

Usage

Sample User Object Validation

const Json = require("schematica").default

const jw = new Json()

const userSchema = jw.createSchema({
    type: "object",
    name: "userSchema",
    required: ["username", "email", "age"], // Validators check if all of these properties are present
    properties: {
        username: {
            type: "string",
            minLength: 3, // String minLength and maxLength values are inclusive
            maxLength: 42
        },
        email: {
            type: "string",
            match: /^\w+([\.-]?\w+)*@\w+([\.-]?\w+)*(\.\w{2,3})+$/ // Strings are able to use regex
        },
        age: {
            type: "number",
            min: 18 
        }
    }
})

// This is the function used to validate objects
// Validators are cached so you can reuse this call without performance loss
const userValidator = jw.buildValidator(userSchema);

const example1 = {
    username: "Casey",
    email: "[email protected]",
    age: 23
}

console.log(userValidator(example1)) // true - all properties are provided and meet their requirements

const example2 = {
    username: "Casey",
    email: "[email protected]",
}

console.log(userValidator(example2)) // false - age is required 

const example3 = {
    username: "Casey",
    email: "[email protected]",
    password: "password1",
    age: 18
}

console.log(userValidator(example3)) // false - password is not defined in the schema and additionalProperties isn't set

Sample Message Object Encoder


const Json = require("schematica").default

const jw = new Json()

// The Key difference between createSchema and addSchema is that addSchema saves the schema with it's ref whereas createSchema doesn't
const userSchema = jw.addSchema({
    name: "userSchema",
    ........
})

const messageSchema = jw.createSchema({
    type: "object",
    required: ["id", "author", "content"],
    properties: {
        id: {
            type: "number"
        },
        author: "$userSchema",
        content: {
            type: "string",
            minLength: 32,
            maxLength: 2048
        }
    }
})

// Build a serializer function, this function takes an object and returns a string
const messageStringify = jw.buildSerializer(messageSchema)

const example1 = {
    id: 1,
    author: {
        username: "John Doe",
        email: "[email protected]",
        age: 27
    },
    content: "Hello Everyone! My name is John Doe and I love cats"
}

console.log( messageStringify(example1) ) 
// {"id":1,"author":{"username":"John Doe","email":"[email protected]","age":27},"content":"Hello Everyone! My name is John Doe and I love cats"}

const example2 = {
    id: 2,
    author: {
        username: "Jane Doe",
        email: "[email protected]",
    },
    content: "How's it going? My name is Jane and I hate cats"
}

console.log( messageStringify(example2) ) // Throws `ERR_INVALID_DATA` because the user schema is missing the property `age`

Documentation