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

tealina

v2.2.2

Published

A CLI for build end-to-end typesafety APIs, and code, types, document generation

Readme

Tealina is a code generation CLI tool that helps you:

  • Generate routing mappings from your API directory structure
  • Create TypeScript types from your Prisma schema
  • Generate API documentation from your API type definitions

Basic Setup

Tealina requires a root API directory to generate route mappings. We recommend using API version aliases (e.g., api/v1v1):

// package.json
{
  "scripts": {
    "v1": "tealina src/api-v1"
  }
}

Generate Route Mapping (-a)

The generation follows a specific file structure convention:

  • First layer: API version or prefix (e.g., api-v1)
  • Second layer: HTTP methods (e.g., get, post, put)
  • Deeper layers: Endpoint handler files (e.g., health.ts, user/login.ts)

Each method directory contains an index.ts that exports its routes, and the API root has an index.ts that aggregates all methods.

Example structure:

api-v1/
  |- get/
  |   |- health.ts
  |   |- index.ts
  |- post/
  |   |- user/
  |   |   |- login.ts
  |   |- index.ts
  |- index.ts

get/index.ts:

export default {
  '/health': import('./health.ts'), // route : handler
}

api-v1/index.ts:

export default {
  'get': import('./get/index.ts'),
  'post': import('./post/index.ts'),
}

Run with -a to generate/update route mappings. The CLI will automatically maintain all index.ts files according to your structure. Route parameters are wrapped in brackets: [id].

pnpm v1 -a

Generate Types (gtype)

Reads your prisma/schema.prisma file and generates TypeScript types for all models, types, and enums. For better composability, relation fields are omitted—only pure types are generated.

pnpm v1 gtype

Generate API Documentation (gdoc)

Parses your exported API types (from types/api-v1.ts) to generate documentation. Your ApiTypeRecord should follow this structure:

export type ApiTypeRecord = {
  get: {
    health: {
      body?: unknown
      headers?: unknown
      params?: unknown
      query?: unknown
    }
  },
  post: {
    // ...
  }
}
pnpm v1 gdoc

Tips

  • Use the scaffolding CLI create-tealina to start a new project from scratch
  • For advanced configuration and detailed documentation, visit the official Tealina documentation