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

@v1nvn/md

v0.55.2

Published

Send a Markdown reply to the Markdown-Viewer as a #share= URL — the md-send CLI behind the md plugin.

Readme

@v1nvn/md

The home of the md plugin — and its plugin root: the md-send CLI in src/, the mod's hooks module at hooks/register.ts (.ts/.tsx the engine loads directly, no build), engine tests at tests/. It sends a Markdown reply — the last one, - on stdin, or any Markdown file — to a self-hosted Markdown-Viewer as a #share= URL, opens the page, and copies the link.

User-facing docs: root README.

Quickstart

In Claude Code, the plugin is the way in — a mod serves the two surfaces the model never reads: /md-edit (editable) and /md-view (read-only) exec the shipped CLI and show its status line as a dim transcript row (nothing execs until a command runs).

claude plugin marketplace add v1nvn/agentic
claude plugin install md@agentic

In a terminal, last reply or a named file:

npx -y @v1nvn/[email protected]              # editable — both panes
npx -y @v1nvn/[email protected] --view       # read-only — preview pane only
npx -y @v1nvn/[email protected] reply.md

Usage

| Invocation | Does | | ---------------------------------- | ---------------------------------------------------------------------------- | | /md-edit | the previous assistant reply → viewer, edit pane enabled, one dim status row | | /md-view | the same share read-only — preview pane only | | npx -y @v1nvn/[email protected] | the same share, printed bare | | npx -y @v1nvn/[email protected] --view | read-only share | | npx -y @v1nvn/[email protected] reply.md | that file instead of the last reply | | npx -y @v1nvn/[email protected] - | Markdown from stdin |

MD_VIEWER_URL sets the viewer (default https://md.v1n.space); any set MD_NO_OPEN value (not just 1) skips opening the browser.

Develop

yarn workspace @v1nvn/md test       # the CLI side (vitest)
claude plugin validate packages/md  # the mod, as the engine reads it
claude plugin test packages/md      # the mod, through the engine
yarn lint && yarn typecheck         # from the repo root (typecheck
                                    #   covers tsconfig.mods.json too)

The mod API is early access and moves between Claude Code releases — a build that refuses the module loads nothing, so validate after every engine update and re-vendor types/claude-code.d.ts (repo root) from the engine-laid .claude-plugin/types/ when it changes. Read references/mods.md first.

Modules

| File | Role | | ------------------- | --------------------------------------------------------------------------- | | src/index.ts | bin entry (md-send) — dispatch, exit codes | | src/share.ts | the #share= URL, browser open, clipboard, status line | | hooks/register.ts | the mod: registers /md-edit and /md-view, execs the CLI, shows its line | | src/index.ts | the CLI source the mod execs — node runs it directly, nothing built |

Contracts

  • One status line of output (e.g. Opened in Markdown-Viewer (link copied).).
  • The document reaches only the configured viewer — no third-party service.
  • /md-edit and /md-view are each one node <plugin root>/src/index.ts exec through the session's Bash tool (/md-viewadds--view) — the same share npx md-sendruns. The one allow rule both need isBash(node /src/index.ts:*)`; the first run asks for it once, then it is remembered. Its status line is a dim transcript row the model never reads.