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

usingenv

v4.0.0

Published

Run commands with a .env file using a clean CLI syntax (using .env.file run command)

Downloads

377

Readme

usingenv

Run any command with a specific .env file using a simple, readable syntax.

No manual exporting. No messy shell commands. Just run it.


What this does

usingenv lets you execute any command while automatically loading environment variables from a file.

Instead of doing this:

dotenv -e .env.vercel -- python manage.py runserver

You can do:

using .env.vercel run python manage.py runserver

That’s it.


Why this exists

Working with multiple environments is painful:

  • .env.local
  • .env.dev
  • .env.staging
  • .env.production

Switching between them usually means long commands or manual exports.

usingenv removes that friction.


Installation

npm install -g usingenv

Usage

Basic usage

using .env.file run your command here

Alternate separator

using .env.file -- your command here

Help and version

using --help
using --version

Examples

Run a Node app:

using .env.local run node app.js

Run a Django server:

using .env.dev run python manage.py runserver

Run Make commands:

using .env.vercel run make runserver

How it works

  1. Reads your .env file
  2. Loads variables into memory
  3. Runs your command with those variables available
  4. Stops cleanly when your command exits

Nothing leaks into your terminal session.


Requirements

  • Node.js 18 or higher

Notes

  • This does NOT modify your system environment permanently
  • Each command runs in its own isolated environment
  • Safe to use for local development and CI scripts

License

MIT