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

telaio

v1.15.2

Published

A highly configurable, TypeScript-first Fastify framework

Readme

Test npm version

Telaio

A TypeScript-first Fastify 5 framework with a builder pattern and phantom types for compile-time feature safety.

Philosophy

Telaio is deliberately opinionated. It selects the libraries, the patterns, and the project layout. There are no adapters for alternative ORMs, alternative loggers, or alternative validation libraries. The stack is fixed: PostgreSQL via Kysely, Redis, pg-boss, Pino, Zod, TypeBox, and AWS SDK where applicable.

The tradeoff is explicit: in exchange for accepting these choices, you get deep type integration, a consistent project structure, and zero configuration overhead for the decisions the framework has already made. If you need to swap out Kysely for Prisma or Redis for Memcached, this is not the right tool.

The centerpiece of the design is phantom types on the builder. Enabling a feature changes the TypeScript type of the built application. Calling app.db without having called .withDatabase() is a compile-time error, not a runtime one. The type system enforces that your wiring is correct before the process starts.

This design has a second-order benefit: it makes your codebase dramatically easier for AI coding agents to work with. A fixed stack means an LLM cannot make wrong library choices. Phantom types and Zod config validation catch its mistakes at compile time, not runtime. The entire application's infrastructure story fits in a single builder chain -- not scattered across dozens of config and module files. The surface area an AI agent needs to understand shrinks to your business logic.

TypeScript is required. ESM is the only module format. Node 20 or later is the minimum runtime.

Install

pnpm add telaio

Documentation

Full docs at https://telaio.niranjan.io -- quick links:

License

MIT