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

@tc39/data-process

v1.0.0

Published

TC39 process data

Downloads

26

Readme

@tc39/data-process Version Badge

github actions coverage License Downloads

npm badge

TC39 process data, public source of truth.

The package exports an array of the stages of the TC39 process, in ascending order. Each stage has its stage number (as a string, e.g. "2.7"), a status describing what it means for a proposal to be at that stage, its entranceCriteria, and its purpose. The latter two are plain text that may contain a newline-separated Markdown bullet list.

Example

import stages from '@tc39/data-process' with { type: 'json' };

stages.map((stage) => stage.stage); // ['0', '1', '2', '2.7', '3', '4']
const stages = require('@tc39/data-process');

The package is a JSON module, so ESM consumers must include the with { type: 'json' } import attribute. TypeScript does not report its absence, but node will throw at runtime without it.

Types

TypeScript declarations are included: the exported value is a Stages tuple with one Stage per stage of the process, in ascending order, so stages[3].stage is known to be "2.7".

import type { Stage, Stages } from '@tc39/data-process';

Schema

schema.json is a JSON Schema (draft 2020-12) describing index.json, and is importable as @tc39/data-process/schema.json. It is the source of truth for the shape of the data: the data is validated against it, and the type declarations are generated from it. It pins each stage to its position, so a missing, duplicated, extra, or out-of-order stage fails validation.