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

@dragonwize/opencode-event-shell-exec

v0.1.0

Published

OpenCode plugin that executes shell commands when configured events are triggered.

Downloads

37

Readme

opencode-event-shell-exec

OpenCode plugin that executes shell commands when configured events are triggered.

Installation

Add the plugin to your opencode.json:

{
  "plugin": ["@dragonwize/opencode-event-shell-exec"]
}

Configuration

Create an opencode-event-shell-exec.json file in either (or both) of these locations:

| Location | Path | Scope | |---|---|---| | Global | ~/.config/opencode/opencode-event-shell-exec.json | All projects | | Project | <project-root>/opencode-event-shell-exec.json | Single project |

Both files are optional. When both exist, command arrays for the same event pattern are concatenated (global first, project second).

Config format

The config file is a JSON object mapping event patterns to arrays of commands:

{
  "session.idle": [
    "notify-send 'OpenCode session completed!'"
  ],
  "session.*": [
    "echo '[{event.type}] at $(date)' >> /tmp/opencode-sessions.log"
  ],
  "*": [
    "echo '{event.type}' >> /tmp/opencode-all-events.log"
  ]
}

Event patterns

| Pattern | Matches | |---|---| | session.idle | Only the session.idle event | | session.* | Any event starting with session. (session.idle, session.created, etc.) | | * | Every event |

When multiple patterns match an event, all matching groups run in parallel. Commands within each group run sequentially.

Available events

  • command.executed
  • file.edited, file.watcher.updated
  • installation.updated
  • lsp.client.diagnostics, lsp.updated
  • message.created, message.updated, message.part.updated
  • permission.requested, permission.replied
  • server.session.updated
  • session.created, session.idle, session.compacted, session.deleted, session.error, session.updated
  • todo.updated
  • tool.execute.before, tool.execute.after
  • tui.file.open

Command entries

Each command in the array can be either a string or an object:

String (simple):

"echo 'hello world'"

Object (advanced):

{
  "command": "echo 'hello world'",
  "cwd": "/tmp",
  "env": { "LOG_LEVEL": "debug" },
  "timeout": 5000
}

| Field | Type | Required | Description | |---|---|---|---| | command | string | Yes | The shell command to execute | | cwd | string | No | Working directory for the command | | env | object | No | Extra environment variables (merged with process.env) | | timeout | number | No | Timeout in milliseconds; command is killed if exceeded |

Interpolation

Environment variables are substituted at config-load time:

{
  "session.idle": ["{env:NOTIFY_COMMAND} 'Session done!'"]
}

Event data is substituted at execution time:

{
  "*": ["echo 'Event: {event.type}' >> /tmp/events.log"]
}

| Token | Replaced with | |---|---| | {env:VAR_NAME} | Value of environment variable (empty string if unset) | | {event.type} | The event type string (e.g. session.idle) | | {event.properties.xxx} | Dot-path into the event object | | {event} | JSON-stringified entire event object |

Execution

Commands run via Bun's shell API, which is cross-platform and prevents shell injection by default. Commands are run with .nothrow().quiet() so failures are logged (via client.app.log) rather than thrown.

Example config

See opencode-event-shell-exec.example.json for a full example.

Development

bun install
bun test
bun run typecheck

License

MIT