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/rm

v0.55.2

Published

Beam a Markdown reply to a reMarkable as EPUB — the rm-send CLI behind the rm plugin.

Readme

@v1nvn/rm

The home of the rm plugin — and its plugin root: the rm-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 beams a Markdown reply — the last one, or any Markdown file — to a reMarkable as EPUB over ssh/scp, then reports the single Sent: line.

User-facing docs: root README.

Quickstart

In Claude Code, the plugin is the way in — a mod serves the one surface the model never reads: /rm-send execs the shipped CLI and shows its Sent: line as a dim transcript row (nothing execs until the command runs).

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

In a terminal, last reply or a named file:

npx -y @v1nvn/[email protected]
npx -y @v1nvn/[email protected] reply.md

Usage

| Invocation | Does | | ---------------------------------- | ---------------------------------------------------------------------- | | /rm-send | the previous assistant reply → EPUB on the device, one dim Sent: row | | npx -y @v1nvn/[email protected] | the same beam, printed bare | | npx -y @v1nvn/[email protected] reply.md | that file instead of the last reply |

Needs pandoc locally and ssh/scp access to the device — REMARKABLE_HOST, default remarkable; the device directory is REMARKABLE_DIR, default /home/root/books.

Develop

yarn workspace @v1nvn/rm test       # the CLI side (vitest)
claude plugin validate packages/rm  # the mod, as the engine reads it
claude plugin test packages/rm      # 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 (rm-send) — dispatch, exit codes | | src/send.ts | pandoc → EPUB → scp, and the Sent: line | | hooks/register.ts | the mod: registers /rm-send, execs the CLI, shows its line | | src/index.ts | the CLI source the mod execs — node runs it directly, nothing built |

Contracts

  • One line of output on success; failures print the failing stage.
  • Nothing is left on the local machine — the EPUB streams to the device.
  • /rm-send is one node <plugin root>/src/index.ts exec through the session's Bash tool — the same beam npx rm-sendruns. The one allow rule it needs isBash(node /src/index.ts); the first run asks for it once, then it is remembered. Its Sent:` line is a dim transcript row the model never reads.