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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@schema-kit/tscodegen

v1.5.0

Published

Generate TypeScript code using Schema Kit

Readme

TypeScript code generator for Schema Kit

About Schema Kit

Schema Kit allows you to create a meta-schema that can be transformed into TypeScript, JSON Schema, and more.

Usage

| Schema Kit | TypeScript | -------------------- | ---------------------------- | never() | never | any() | any | buildConst(value) | type Title = value | buildNull() | null | boolean() | boolean | number() | number | integer() | number | string() | string | stringEnum(values) | enum Title {} | optional(schema) | Union with undefined. Optional property if inside an object. | object(props) | interface Title {} | array(schema) | T[] | union(schemas) | The union of the schemas

import { toTypescriptCode } from "@schema-kit/tscodegen"

toTypescriptCode(schema, opts)

function toTypescriptCode<O extends BaseSchema>(
  schema: Schema<O>,
  opts: ToTypescriptCodeOptions<O>
): string

Converts the input schema into TypeScript code.

Type parameters:

  • O - User-defined schema types.

Parameters:

  • schema: Schema<O> - The input schema.
  • opts: ToTypescriptCodeOptions<O> = { prettier: { filepath: "file.ts" } }
    • prettier?: prettier.Options - Options to pass to Prettier
    • overrideResolvers?(defaultResolvers) - Override the resolvers used.

Returns: string - The output TypeScript code.

Technical limitation: Currently all object and stringEnum schemas generate interfaces and enums. Interfaces and enums without a title are given a deterministically-generated ID prefixed with __.

overrideResolvers

Useful if you want to override the resolvers used to resolve types, e.g. if you have a custom node type. The function takes the key-value object of default resolvers. You must return a similarly-typed object with your own resolvers. Do not mutate the set of default resolvers!