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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@remscodes/env-mode

v1.1.1

Published

A tiny, handy and strongly typed library for working with the env mode (NODE_ENV)

Downloads

8

Readme

github ci npm version bundle size license

Installation

npm install @remscodes/env-mode

Note

This library does not load environment variables from a .env files.

It is supposed to be used in addition to any module or framework that load these variables.

Usage

// .env
NODE_ENV=dev

Current value

Get the env mode value.

import EnvMode from '@remscodes/env-mode';

EnvMode.get(); // "dev"
EnvMode.getOrThrow(); // "dev"

Conditions

Build conditions based on the env mode.

import EnvMode from '@remscodes/env-mode';

EnvMode.is('dev'); // true
EnvMode.isNot('dev'); // false

EnvMode.in(['dev', 'prod']); // true
EnvMode.notIn(['dev', 'prod']); // false

Selection

Select a specific value depending on the env mode.

import EnvMode from '@remscodes/env-mode';

const color = EnvMode.select({ // "blue"
  dev: 'blue',
  default: 'red',
});

Typed usage

Create a declaration file and add all your env mode values as follows.

// global.d.ts 
declare global {
  namespace NSEnvMode {
    interface ModeMap {
      dev,
      prod,
    }
  }
}

export {};

Include it into your tsconfig.json.

// tsconfig.json
{
  // ...
  "include": [
    "global.d.ts"
  ]
}

Now your env modes can be autocompleted through methods.

Configuration

Throw

By default, if the env mode is empty (undefined or ""), the methods work with this empty value.

You can choose to throw an exception from every methods if env mode is empty.

Example :

// .env
NODE_ENV=
EnvMode.is('dev'); // false
EnvMode.configure({ throwIfEmpty: true });
EnvMode.is('dev'); // [EnvModeException: "NODE_ENV" is not defined in "globalThis.process.env".]

Key

By default, it works with the NODE_ENV key.

You can change it as follows.

Example :

// .env
DENO_ENV=dev
EnvMode.configure({ key: 'DENO_ENV' });
EnvMode.get(); // "dev"

Source

By default, it works with the globalThis.process.env source.

You can change it as follows.

Example :

// environment.ts
export const myEnvironment = {
  NODE_ENV: 'dev',
};
import { myEnvironment } from './environement.ts';

EnvMode.configure({ source: myEnvironment });
EnvMode.get(); // "dev"

License

MIT © Rémy Abitbol.