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

codeshape

v3.1.5

Published

Code postprocessing utility: typecheck, lint, format, compile, emit types

Readme

codeshape

Code postprocessing utility, a thin abstraction layer over evolving toolsets.

Usage: npx codeshape [...space-separated tasks] [...--flags]

Default entry point: ./index.ts

Performed tasks:

  • typecheck (with tsgo from @typescript/native-preview)
  • lint, format (with @biomejs/biome)
    • use --no-commit to skip the fix commit
    • use -m <message> to set a fix commit message (default: lint)
    • use --vcs-disabled to opt out from using .gitignore
    • use a .lintignore plain-text file to list specific path patterns to be ignored by this task (in a format similar to .gitignore)
    • use a .lintinclude plain-text file to list specific path patterns to be handled by this task (in a format similar to .gitignore) (default: the entire current directory), mark excluded paths with a leading ! in this file
  • compile (with tsdown)
    • use --no-dts to skip emitting a type declaration file
    • use --esm-only to produce only an ESM .js file (default: ESM .mjs and CJS .cjs)
    • use --compile-input <...space-separated paths> (default: ./index.ts) and --compile-output <path> (default: ./dist) to set an entry point and an output directory
    • use --compile-platform to set a target platform (default: node, other options: browser, neutral)
    • use --minify to minify the output
    • use --tsconfig <path> to point to a custom TS config file

Use npx codeshape check as a shorthand version of npx codeshape typecheck lint format.

Example 1: npx codeshape runs typechecking, linting, formatting, adds a fix commit if needed, compiles ./index.ts to ./dist/index.mjs and ./dist/index.cjs, emits type declarations to ./dist/index.d.ts.

Example 2: npx codeshape check --no-commit runs typechecking, linting, formatting (without adding a fix commit).

Example 3: npx codeshape typecheck runs typechecking.

Any of these one-liners can be run in a directory or added to package.json scripts without manually installing packages.