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

typeables

v0.1.2

Published

Little runtime JSONSchema+TypeScript types

Readme

Typeables

Little runtime JSONSchema types.

What this is

Let’s say you write a nice TypeScript application. But, the type-safety disappears at runtime: TypeScript compiles to JS and then disappears. But now maybe you want to do some sort of JSON.parse(file) type of behavior. Or, maybe your app has environment variables that just are assumed to be there. What do you do?

Well, what most people do is to just use that JSON.parse() function, it returns an any, and they let the program crash when the input is invalid.

Let’s suppose you want a stronger guarantee.

So then in practice you would repeat yourself: you have a JSONSchema description of your type, present at runtime, used to validate data and fail fast on bad inputs, and a TypeScript version of your type, present at compile time, used to make your code more reliable. Then, problems occur when you update one of these and not the other—they are only joined by an any type, so anything goes.

A typeable is a JavaScript object—it is present at runtime—which describes a type. You construct it with functions exposed by this library. However, at compile-time it corresponds to a specific TypeScript type and can even generate random data of the appropriate type.