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

@jexsrs/dot2env

v1.0.0

Published

This library allows the user to read different `.env` files based on the environment variable (`NODE_ENV`).

Downloads

2

Readme

dot2env | dotenv environment

This library allows the user to read different .env files based on the environment variable (NODE_ENV).

This project was inspired from dotenv.

Install

npm install dot2env

Usage

Simple

Create a .env file in the root of your project:

USERNAME="jex"
password="secret"

As early as possible in your application, import and configure dot2env:

import "@jexsrs/dot2env";

console.log(process.env.USERNAME);
console.log(process.env.PASSWORD);

Environments

The supported environments are:

  • production, prod
  • staging, stage
  • testing, test
  • development, dev

For each environment you will have to create a .env.[environment] file (using the full name).

Now everytime you call your application using an environment, it will automatically import all the variables in that file.

For example, running:

NODE_ENV=production node index.js

will import only the .env.production file.

If the .env.[environment] file is not found, it will always fallback to the .env file.

Override default variables

If you want to override existing environment variables, use the override option.

import {load} from "@jexsrs/dot2env";

load({override: true});

Custom mapping

In case you want to add more environments or use custom ones you can define your own mapping:

import {load} from "@jexsrs/dot2env";

load({
    envMap: {
        development: '.env.development',
        testing: '.env.testing',
        staging: '.env.staging',
        production: '.env.production',
        'custom-env': '.env.custom-environment'
    }
});