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

@usama8800/dotenvplus

v3.4.0

Published

Dotenv+

Downloads

151

Readme

Dotenv+

Dotenv+ reads .env and mode.env files and returns them as an object. You can pass in a zod schema which will pe parsed against the keys in the env files. You can alos set required keys with conditions (check the type).

This package also export a zod schema booleanSchema which makes 1 and true equal to true and everything else false

Usage

import { loadEnv, booleanSchema } from '@usama8800/dotenvplus';
import { z } from 'zod';

const env = dotenvPlus({
  schema: z.object({
    PORT: z.coerce.number().default(8000),
    MODE: z.enum(['dev', 'prod']).default('dev'),
    LOGGING: booleanSchema.default(true),
    DERIVED_MODE_FULL: z.string().default(''),
  }),
  transform: (data) => {
    if (data.MODE === 'prod') data.PORT = 80;
    data.DERIVED_MODE_FULL = data.MODE === 'dev' ? 'development' : 'production';
    return data;
  }
});

There are two ways to use dotenv+:

  • Using imports
  • Changing modes You can use both at the same time.

.env file is always loaded

Any time a file is loaded, it's local file (local.env or local.MODE.env) is also loaded. Add local files to .gitignore and commit non local env files.

MODE.env files are loaded only if MODE is set either in .env or from an environment variable.

Depending on localType and modeType given in loadEnv() function, files names can be like local.MODE.env, MODE.env.local, or .env.MODE.local with or without local or MODE.

Using imports

# .env
KEY1=VAL1
import database
import common

# database.env
CONNECTION_STRING=localhost

# common.env
import ports
SECRET=VAL2

# ports.env
PORT=3000

Imports are replaced with the content of the file expect lines which set MODE

Changing modes (Old)

# .env
KEY1=VAL1
MODE=production

# production.env
CONNECTION_STRING=localhost
PORT=3000
MODE=common

# common.env
KEY2=VAL2

When MODE is set in a file, after the file is loaded, MODE.env is loaded until MODE does not change.