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

@w32191/hashline-plugin

v0.1.5

Published

OpenCode plugin that adds hashline-aware read and edit behavior.

Downloads

57

Readme

@w32191/hashline-plugin

Hashline plugin for OpenCode that adds hashline-aware read output and guarded edit operations.

Behavior contract

Hashline is designed to reduce harness failures by giving the agent stable line anchors during read, then rejecting stale edits before file corruption.

Read output is rewritten into this format:

11#VKQT|function hello() {
12#XJMB|  return "world"
  • The visible hash token is 4 characters.
  • The edit tool is replace-only: each edit targets a required line#hash anchor and replaces that anchored line with zero or more lines.
  • lines: null deletes the anchored line.
  • lines: ["a", "b"] replaces one anchored line with multiple lines.

Normalization trade-off

Hashline anchors are computed from the line number plus normalized line content:

  • carriage returns are ignored for hashing
  • trailing whitespace is trimmed for hashing
  • visible read output content is preserved as displayed

This is intentional: Hashline optimizes for stable, verifiable agent edits rather than byte-perfect whitespace identity.

Upgrade note

The current contract uses 4-character visible hash tokens. If you upgrade from an older 2-character token release, agents must reread files before attempting hashline edits.

Configure in opencode.json

According to the official OpenCode plugin docs, npm plugins are configured with the singular plugin key in opencode.json.

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["@w32191/hashline-plugin"]
}

Notes:

Loader compatibility

  • src/index.ts exports a named server plugin function (and keeps default export for backward compatibility).
  • package.json declares oc-plugin.targets with server so OpenCode npm loader can discover the server target.

Package contents

  • dist/index.js: bundled plugin entrypoint
  • dist/index.d.ts: published type declarations

Release

See docs/release-runbook.md for the GitHub Actions release flow.