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

@markdy/cli

v0.8.3

Published

First-party CLI for MarkdyScript diagrams: lint, format, explain, render, and a local playground.

Readme

@markdy/cli

First-party command-line tooling for MarkdyScript.

Install

npm i -D @markdy/cli

If you install it into a project, run it with npx markdy ... or npm exec markdy ... from that project. To make markdy available as a shell command everywhere, install it globally with npm i -g @markdy/cli.

Package position (text)

@markdy/cli
	-> reads .markdy files from disk
	-> uses parser/runtime packages internally
	-> outputs diagnostics, formatted source, or rendered HTML

Output preview

Use this command to generate a local HTML preview:

npx markdy render examples/showcase/bullet-reveal.markdy --out examples/xscene.html

Commands

markdy                 # launch a local browser playground on http://127.0.0.1:4242
markdy lint scene.markdy
markdy fmt scene.markdy
markdy fmt scene.markdy --write
markdy render scene.markdy --out dist/scene.html
markdy explain scene.markdy
markdy new explainer demo.markdy
markdy docs
markdy ai
markdy check-all .

Notes

  • The CLI resolves import "file.markdy" as ns from disk before parsing.
  • fmt prints a canonicalized scene and may expand higher-level sugar into its parsed form.
  • render --out writes a self-contained HTML preview to the exact path you pass in.
  • If the path is relative, it is resolved from the current working directory.
  • If you see zsh: command not found: markdy, the package is installed locally but that directory is not on your PATH.