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

@markset-lang/diagram-ascii

v0.4.2

Published

Draws an ASCII diagram fence as SVG (spec §10). An engine, not part of the renderer.

Readme

@markset-lang/diagram-ascii

Draws an ASCII diagram as SVG. A pure function with no dependencies: text in, SVG out.

npm i @markset-lang/diagram-ascii
# or
pnpm add @markset-lang/diagram-ascii
import { drawAscii } from "@markset-lang/diagram-ascii";

const svg = drawAscii(`
+--------+      +--------+
| ingest | ---> | index  |
+--------+      +--------+
`);

Returns the SVG markup as a string, or null when there is nothing to draw.

What it draws

A deliberately small subset, written down so it can be relied on:

-  horizontal line        +  corner or junction
|  vertical line          /  \  diagonal
>  <  ^  v  arrowheads, recognized only where a line actually arrives

Everything else is text, set in a monospace face at the cell it occupies. There is no box detection, no layout, and no attempt to be svgbob: the diagram is drawn exactly where the author put it, cell by cell, so what renders is what is in the file. A lone - between two letters is part of a word, not a rule, so us-east stays a word.

The SVG carries its own prefers-color-scheme block and follows the embedding page's color-scheme, so a diagram in a forced light or dark page matches it.

Why ASCII

This is the default diagram engine of @markset-lang/render-html, and the only one the reference implementation ships. Spec §10 says why: every other diagram source falls back to its own source code when it cannot be drawn, which is honest but is not a diagram. ASCII falls back to a diagram, because it already was one — in a terminal, a diff, a GitHub comment, or the downgraded document. It is the one common diagram source whose undrawn form is as good as its drawn form.

In Markset a fence is drawn only inside a captioned figure, because the caption is the text alternative a drawn picture needs. That rule is the renderer's, not this package's; this function draws whatever it is given.

Using it elsewhere

Nothing here knows about Markset. It is a string-to-string function that a static site generator, a documentation tool, or a test can call directly.

Specification: https://markset.org/spec/. Source: https://github.com/markset-lang/markset.

MIT.