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

@type-atlas/atlascii

v1.0.0

Published

ASCII components for code intelligence: locations, navigation targets, call hierarchies, outlines, diagnostics, and source frames as plain text.

Readme

@type-atlas/atlascii

ASCII components for code intelligence.

Renders the shapes a language server produces — locations, navigation targets, call hierarchies, outlines, diagnostics, source frames — as plain text meant to be read by an agent from a transcript.

What it is

Pure functions. Data in, string out. No colour, no terminal, no framework, no document layer. Every component takes the protocol's own values — an LSP Range, a severity number — and does the formatting itself, so a caller never formats anything before calling.

That constraint is the whole design. A component that took "12:7-12:18" instead of a Range would be asking its caller to do the library's job, and would leave every consumer with its own copy of the zero-based-to-one-based conversion. Here that conversion exists once, in range.ts.

Layers

source-offset.ts   position ↔ offset arithmetic. No strings at all.
range.ts           positions and ranges as text. One conversion point.
                   ↑ everything below builds on these

code-frame.ts      source excerpt with a gutter and span carets
locations.ts       located rows grouped by file (ripgrep --heading -n)
targets.ts         navigation targets (❯ file:line:col)
calls.ts           call hierarchy, one file, indented callables
symbols.ts         document outline, ctags kinds, depth nesting
workspace-symbols.ts   symbol search hits with containers
diagnostics.ts     compiler-style problems

divider.ts         section rule, centred or right-anchored text
summary.ts         right-aligned label column, singular/plural
time.ts            durations that stop being milliseconds past a second

Prior art

The layout primitives are adapted from Vitest's reporters — divider, padSummaryTitle, formatTime, the code frame's gutter and caret arithmetic, the frame, and the rule that a row never prints a zero state. Vitest solves the same problem this does: dense, scannable, colour-optional text about code, read quickly by someone who did not write it.

The transplanted source is kept at packages/core/src/markdoc/format/vitest-reference/ with an extraction log.

Status

Early. The components here are in use by Type Atlas, an MCP server for TypeScript code intelligence, which is where each one was shaped against real agent-facing output rather than designed in advance.

Not yet extracted from that project: the diff body (-/+ unified lines), state glyphs, count lines, stack frames, breadcrumbs, tree rows, and an indented-block writer.