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

@jswork/dotenv-local-first

v1.0.4

Published

Dotenv local first cli.

Readme

dotenv-local-first

Dotenv local first cli.

Installation

yarn add --dev @jswork/dotenv-local-first

Usage

This CLI tool loads environment variables from .env* files with the following priority (later files override earlier ones):

  1. .env
  2. .env.${NODE_ENV} (e.g., .env.development, .env.production)
  3. .env.local
  4. .env.${NODE_ENV}.local (e.g., .env.development.local)

Basic usage

# Just load and display environment variables
dotenv-local-first

# Run a script with loaded environment variables
dotenv-local-first your-script.js

# Run with verbose logging
dotenv-local-first -v your-script.js

Example

Create your environment files:

# .env (base configuration)
DATABASE_NAME=myapp_db
DATABASE_USER=root
DATABASE_PORT=3306
DATABASE_PASS=secret123

# .env.development (development overrides)
DATABASE_NAME=myapp_dev_db
DATABASE_PORT=3307
DATABASE_PASS=dev_secret

# .env.local (local overrides - should not be committed)
DATABASE_PASS=local_override_password
DATABASE_USER=local_user

Then run:

NODE_ENV=development dotenv-local-first

This will load variables with the priority: .env → .env.development → .env.local → .env.development.local

Development

bun create cli/dotenv-local-first --no-git --no-install