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

pi-dotenv

v1.0.1

Published

Load ~/.pi/agent/.env into process.env at pi startup

Readme

pi-dotenv

Load ~/.pi/agent/.env into process.env at pi startup.

Install

pi install npm:pi-dotenv

Or install from a local path:

pi install /path/to/pi-dotenv

Usage

Create ~/.pi/agent/.env:

TAVILY_API_KEY=tvly-...
AGENTMAIL_API_KEY=...
XYZ_API_KEY=fake_123

Restart pi. Existing shell env vars are never overwritten.

Load order

pi-dotenv loads the file when pi loads the extension. An extension that reads process.env when pi loads it (not in an event handler) sees these values only if pi-dotenv loads first. Put npm:pi-dotenv first in packages in ~/.pi/agent/settings.json. Extensions from pi -e, .pi/extensions/, ~/.pi/agent/extensions/, and project packages always load before global packages. Extensions that read process.env in session_start or later are not affected.

How it works

  • Loads the dotenv file at extension load (factory time), so extensions that read process.env while pi loads are already served; reloads on each session_start (idempotent, picks up edits across /new, /resume, /fork)
  • Uses @dotenvx/dotenvx with processEnv: {} (no ambient variable interpolation)
  • Never overrides an env var already set in the shell
  • Synchronous, minimal, zero network calls