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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@btboy/dotenv

v1.0.3

Published

Loads environment variables from files whose name start with .env

Downloads

8

Readme

The package is a zero-dependency module that loads environment variables from files whose name start with .env:

  • .env.[process.env.NODE_ENV].local
  • .env.local
  • .env.[process.env.NODE_ENV]
  • .env

The package will read these files, parse data with variable / value, then put into process.env.

Same variable's name between diferent .env files will take precedence: .env.[process.env.NODE_ENV].local > .env.local > .env.[process.env.NODE_ENV] > .env. For Example:

in .env.production.local

DB_SECRET=1234

in .env.local

DB_SECRET=abc

DB_SECRETE=1234 will work.

How it work

Let's say that you have set process.env.NODE_ENV = "development", and then this package will read .env.development.local, .env.local, .env.development, .env one by one, ingore files which not exist, parse every line to key/value, join into one map, and put into process.env.

Install

$ npm install -i @btboy/dotenv

Usage

import initEnv from "@btboy/dotenv";

initEnv({});

Options

cwd

Default: process.cwd()

You may specify a custom path your .env files. the module will find them here.

initEnv({cwd: process.cwd()});
Debug

Default: false

You may turn on logging to help debug why certain keys or values are not being set as you expect.

initEnv({Debug: true });
encoding

Default: utf8 You may specify the encoding of your file containing environment variables.

initEnv({encoding: `utf8` });