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

@w33ble/opencode-env-inject

v1.0.1

Published

Readme

opencode-env-inject

OpenCode plugin that injects environment variables from JSON config files into every shell session.

Installation

Copy dist/env-inject.ts to the local or home plugins path.

cp dist/env-inject.ts ~/.config/opencode/plugins/

Configuration

Global Config

Create ~/.config/opencode/env.json:

{
  "MY_API_KEY": "your-api-key-here",
  "NODE_ENV": "development"
}

Local Config

Create .opencode/env.json in your project directory:

{
  "NODE_ENV": "production",
  "DEBUG": "true"
}

Merge Behavior

Local config overrides global config on key conflicts.

In the example above:

  • MY_API_KEY comes from global config
  • NODE_ENV = production (local overrides global)
  • DEBUG = true comes from local config

Usage

Once installed, all shell commands executed through OpenCode will have these environment variables available automatically.

Error Handling

  • Missing config files are ignored gracefully
  • Invalid JSON is ignored with no error
  • Existing environment variables are preserved (not overwritten)

Building

bun run build

Produces dist/index.js (bundle) and dist/index.d.ts (type declarations). @opencode-ai/plugin is external — opencode provides it at runtime.

Publishing

Build first, then publish with bun publish:

bun run build
bun publish --access public

bun publish is Bun's native publish command (not an npm wrapper). The --access public flag is required for public packages. Alternatively, set it once in package.json:

"publishConfig": { "access": "public" }

With files: ["dist"] in package.json, only the build output is shipped — src/, biome.json, tsconfig*.json, and other dev files are excluded.

For local development, symlink the bundle into the opencode plugins dir instead of installing:

ln -sf $(pwd)/dist/index.js ~/.config/opencode/plugins/env-inject.ts

License

Mozilla Public License 2.0