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

opencode-chrome-annotation

v1.0.4

Published

Annotate pages in Chrome and send context into your local OpenCode setup.

Downloads

1,104

Readme

OpenCode Chrome Annotation

version license

Annotate any page in Chrome and send the screenshot, selected element metadata, and your instruction directly into OpenCode.

https://github.com/user-attachments/assets/bdee8a15-6720-4e57-b28d-ee6440722b71

Install

Add the plugin to your OpenCode config:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["opencode-chrome-annotation@latest"]
}

Install the Chrome extension from the Chrome Web Store:

https://chromewebstore.google.com/detail/abeihanpaeioklkhioiigklonbomhjfd

How It Works

  1. Start OpenCode in your project.
  2. Click the extension button in Chrome.
  3. Connect the current tab to your OpenCode session from the in-page picker.
  4. Click Annotate in the in-page pill.
  5. Select an element, write your instruction, and submit.

What Gets Sent

  • Your written instruction.
  • The current page URL and title.
  • Selected element metadata such as selector, tag, text, role, aria label, and bounds.
  • A screenshot saved locally by the plugin and referenced in the OpenCode prompt.

Troubleshooting

The plugin runs a local HTTP server bound to 127.0.0.1 on ports 39240-39260. The extension discovers the active OpenCode plugin instance over localhost.

  • The extension can't start a new session, you need to be in an active OpenCode session to connect.
  • If the extension can't find any session, ask your agent to run chrome_status that should give a detailed report.
  • Make sure OpenCode and your Chromium browser exist in the same localhost network (not in seperate containers).

Development

Plugin

The OpenCode plugin source lives in src/plugin.ts. The published package entrypoint is generated at dist/plugin.js.

Install dependencies:

bun install

Build the plugin:

bun run build

Extension

The Chrome extension source lives in extension-src/. The loadable extension output is generated into extension/ and is not tracked by git.

bun run build:extension

Then load the generated extension/ directory from chrome://extensions.

To create the Chrome Web Store upload zip:

bun run build:zip