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

@gbti/ryker

v0.2.5

Published

Add Ryker inline editing and prompt-ready change requests to authored HTML documents.

Readme

Ryker

Inline editing for HTML and Markdown. Export your corrections as agent-ready instructions a model can learn from.

Ryker is a Chrome extension for editing a document in place and recording every change you make as a prompt-ready change request. A model can draft a report in seconds. What it cannot do is know that the third section should have come first, or that a summary buries its own conclusion. Those corrections are structural and they are yours, and the usual place to make them is back in the prompt, describing a document you are looking at but cannot touch.

Ryker: edit an authored HTML page inline and export the corrections as agent-ready instructions

Watch the three minute walkthrough.

Why inline

HTML has become a useful format for delivering rich content when working with large language models: complete reports, tables, figures, layouts and styled documents, in a form that renders immediately in a browser. Markdown has likewise become a common format for structured content.

Both are easy for a model to generate and awkward to edit at the source. Markdown means switching between source and preview. HTML source separates the author from the rendered document the reader will actually see. Inline editing lets you work against the rendered result instead, and Ryker keeps a record of what you changed while you do it.

Two ways to use it

As a Chrome extension. Click the toolbar button on any HTML page to edit that document in place. Or open the Ryker workspace and load a Markdown or HTML file from your own disk. On a tab Chrome will not let it touch, a new tab or a chrome:// page, the button opens the workspace instead of failing.

Add Ryker to Chrome from the Chrome Web Store, or load it unpacked from extension/.

As a drop-in. Add Ryker to an HTML document with npx and it travels with the file. A reader or reviewer can then edit the page and produce a change request without installing anything.

npx --yes @gbti/ryker insert ./report.html

Features

  • Inline visual editing for HTML and Markdown
  • Export content changes as a machine-readable prompt
  • An outline built from the document's real heading structure
  • Move or delete whole sections from that outline, recorded as moves rather than as character diffs
  • Revision history tracked per document
  • Markdown with nested lists, tables and code fences, returned as the file it came from
  • Save the edited document back over the file you opened, or as a new file beside it

Install into an HTML document

npx --yes @gbti/ryker insert ./report.html

Preview first with --dry-run. The installer creates a recoverable report.html.ryker-backup, copies the dependency-free browser bundle beside the document, and adds one identifiable managed block before </body>.

npx --yes @gbti/ryker doctor ./report.html
npx --yes @gbti/ryker sync ./report.html
npx --yes @gbti/ryker remove ./report.html

insert writes Ryker into the document. doctor checks an existing install and writes nothing: it verifies the managed block is present and correctly placed, and that the bundle matches this version of the package. sync updates an existing install. remove deletes the managed block from that document and retains the browser bundle, because other documents in the same folder may share it.

Ryker requires Node.js 20 or newer for installation. The resulting HTML and classic browser script work offline and from file:// without Node.js.

This repository is at version 0.2.5, and the npm latest tag serves it, so every npx command above installs this code.

Privacy

Ryker keeps its editing history in your own browser and sends nothing anywhere: no server, no account, no sync, no telemetry. The page cannot read it. You can export the record whenever you like and clear it per document.

The extension asks for no standing access to your browsing. It has no host permissions, registers no content scripts, and injects nothing until you click its button. The permission it uses, activeTab, grants access to one tab for one gesture and expires with it.

privacy.md is the full policy, and is the URL the Chrome Web Store listing points at.

License

Ryker is source-available under the custom license included with the package. Internal-team use, internal commercial use and inclusion with client deliverables are permitted. Ryker, its forks and its derivatives may not be sold or shipped or featured as part of a commercial product or software as a service offering without prior written permission from GETHSEMANE LLC. The license and copyright notice must remain intact.

Bugs and issues: https://github.com/gbti-network/ryker/issues

Credits

Wing icon by prasong tadoungsorn from Noun Project, licensed CC BY 3.0.

This credit lives here and in the Chrome Web Store listing, and deliberately nowhere else. Earlier commits placed it more widely and were narrowed later, so a commit message asking for it in other files has been superseded by this line rather than by an oversight. CC BY attribution attaches to distribution, and both places it appears are distributed: this file ships in the npm package, and the listing is public.