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-good-fences

v0.1.0

Published

OpenCode TUI plugin that renders fenced code blocks as a borderless box with a language label.

Readme

opencode-good-fences

Not related to the good-fences TypeScript boundary tool.

An OpenCode TUI plugin that renders fenced code blocks in assistant replies as a borderless box: a subtle raised background, a muted language label in the top-left corner, and the syntax-highlighted code inside.

Scope

  • Styles only Markdown written by the assistant (reply text and compaction summaries). Tool output (bash, read, grep, and so on) is plain text and is never touched.
  • Registers a renderer for every language OpenTUI can normalize (its extension and basename maps, currently ~70 keys) plus a few common aliases (sh, shell, console, text, ...). Language keys are normalized with infoStringToFiletype and deduplicated.
  • Fences with no language tag, or with a language OpenTUI does not know, keep the default look: the Markdown code-block API routes strictly by resolved language and has no wildcard.

Requirements

  • OpenCode 2.x (V2) TUI. Uses context.markdown.registerCodeBlockRenderer.
  • @opentui/core >= 0.8.0 (bundled with OpenCode 2.2.x). Uses BoxRenderable, TextRenderable, extensionToFiletype, basenameToFiletype, infoStringToFiletype.
  • Tested with OpenCode 2.2.5.
  • Not compatible with OpenCode 1.x (V1 plugin API).

Install

Add the package to ~/.config/opencode/cli.json (a package with only a TUI part goes in cli.json, not opencode.json):

{
  "plugins": ["opencode-good-fences"]
}

Restart OpenCode. Check /plugins for load errors, then send a message with a fenced code block to see the result.

Theming

Uses the active theme: background.raised.base for the block surface and text.muted for the language label. It works with any theme and was designed alongside the warm opencode-warm-boot palette.

How it works

setup(context) registers one code-block renderer per known language through context.markdown.registerCodeBlockRenderer, wrapping the default renderable in a BoxRenderable. The returned cleanup unregisters every language.

Uninstall

Remove the entry from cli.json and restart OpenCode.

Development

npm install
npm run build   # tsc -> dist/
npm test        # smoke test against dist/ (renders a frame with @opentui/core testing)

License

MIT