Nozzle Piping Mismatch

    TypeScript icon, indicating that this package has built-in type declarations

    1.1.1 • Public • Published



    orangedenv is a zero-dependency module that loads environment variables from a .env file into process.env. Storing configuration in the environment separate from code is based on The Twelve-Factor App methodology.

    BuildStatus Build status NPM version js-standard-style Coverage Status LICENSE Conventional Commits


    # with npm
    npm install orangedenv
    # or with Yarn
    yarn add orangedenv


    As early as possible in your application, require and configure orangedenv.


    Create a .env file in the root directory of your project. Add environment-specific variables on new lines in the form of NAME=VALUE. For example:


    process.env now has the keys and values you defined in your .env file.

    const db = require('db')
      host: process.env.DB_HOST,
      username: process.env.DB_USER,
      password: process.env.DB_PASS


    You can use the --require (-r) command line option to preload orangedenv. By doing this, you do not need to require and load orangedenv in your application code. This is the preferred approach when using import instead of require.

    $ node -r orangedenv/config your_script.js

    The configuration options below are supported as command line arguments in the format orangedenv_config_<option>=value

    $ node -r orangedenv/config your_script.js orangedenv_config_path=/custom/path/to/your/env/vars

    Additionally, you can use environment variables to set configuration options. Command line arguments will precede these.

    $ orangedenv_CONFIG_<OPTION>=value node -r orangedenv/config your_script.js
    $ orangedenv_CONFIG_ENCODING=latin1 node -r orangedenv/config your_script.js orangedenv_config_path=/custom/path/to/.env


    config will read your .env file, parse the contents, assign it to process.env, and return an Object with a parsed key containing the loaded content or an error key if it failed.

    const result = orangedenv.config()
    if (result.error) {
      throw result.error

    You can additionally, pass options to config.



    Default: path.resolve(process.cwd(), '.env')

    You may specify a custom path if your file containing environment variables is located elsewhere.

    require('orangedenv').config({ path: '/full/custom/path/to/your/env/vars' })


    Default: utf8

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

    require('orangedenv').config({ encoding: 'latin1' })


    Default: false

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

    require('orangedenv').config({ debug: process.env.DEBUG })


    The engine which parses the contents of your file containing environment variables is available to use. It accepts a String or Buffer and will return an Object with the parsed keys and values.

    const orangedenv = require('orangedenv')
    const buf = Buffer.from('BASIC=basic')
    const config = orangedenv.parse(buf) // will return an object
    console.log(typeof config, config) // object { BASIC : 'basic' }



    Default: false

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

    const orangedenv = require('orangedenv')
    const buf = Buffer.from('hello world')
    const opt = { debug: true }
    const config = orangedenv.parse(buf, opt)
    // expect a debug message because the buffer is not in KEY=VAL form


    The parsing engine currently supports the following rules:

    • BASIC=basic becomes {BASIC: 'basic'}
    • empty lines are skipped
    • lines beginning with # are treated as comments
    • empty values become empty strings (EMPTY= becomes {EMPTY: ''})
    • inner quotes are maintained (think JSON) (JSON={"foo": "bar"} becomes {JSON:"{\"foo\": \"bar\"}")
    • whitespace is removed from both ends of unquoted values (see more on trim) (FOO= some value becomes {FOO: 'some value'})
    • single and double quoted values are escaped (SINGLE_QUOTE='quoted' becomes {SINGLE_QUOTE: "quoted"})
    • single and double quoted values maintain whitespace from both ends (FOO=" some value " becomes {FOO: ' some value '})
    • double quoted values expand new lines (MULTILINE="new\nline" becomes
    {MULTILINE: 'new


    Should I commit my .env file?

    No. We strongly recommend against committing your .env file to version control. It should only include environment-specific values such as database passwords or API keys. Your production database should have a different password than your development database.

    Should I have multiple .env files?

    No. We strongly recommend against having a "main" .env file and an "environment" .env file like .env.test. Your config should vary between deploys, and you should not be sharing values between environments.

    In a twelve-factor app, env vars are granular controls, each fully orthogonal to other env vars. They are never grouped together as “environments”, but instead are independently managed for each deploy. This is a model that scales up smoothly as the app naturally expands into more deploys over its lifetime.

    The Twelve-Factor App

    What happens to environment variables that were already set?

    We will never modify any environment variables that have already been set. In particular, if there is a variable in your .env file which collides with one that already exists in your environment, then that variable will be skipped. This behavior allows you to override all .env configurations with a machine-specific environment, although it is not recommended.

    If you want to override process.env you can do something like this:

    const fs = require('fs')
    const orangedenv = require('orangedenv')
    const envConfig = orangedenv.parse(fs.readFileSync('.env.override'))
    for (const k in envConfig) {
      process.env[k] = envConfig[k]

    Can I customize/write plugins for orangedenv?

    For orangedenv@2.x.x: Yes. orangedenv.config() now returns an object representing the parsed .env file. This gives you everything you need to continue setting values on process.env. For example:

    const orangedenv = require('orangedenv')
    const variableExpansion = require('orangedenv-expand')
    const myEnv = orangedenv.config()

    What about variable expansion?

    Try orangedenv-expand

    How do I use orangedenv with import?

    ES2015 and beyond offers modules that allow you to export any top-level function, class, var, let, or const.

    When you run a module containing an import declaration, the modules it imports are loaded first, then each module body is executed in a depth-first traversal of the dependency graph, avoiding cycles by skipping anything already executed.

    ES6 In Depth: Modules

    You must run orangedenv.config() before referencing any environment variables. Here's an example of problematic code:


    import { Client } from 'best-error-reporting-service'
    export const client = new Client(process.env.BEST_API_KEY)


    import orangedenv from 'orangedenv'
    import errorReporter from './errorReporter'
    orangedenv.config() Error('faq example'))

    client will not be configured correctly because it was constructed before orangedenv.config() was executed. There are (at least) 3 ways to make this work.

    1. Preload orangedenv: node --require orangedenv/config index.js (Note: you do not need to import orangedenv with this approach)
    2. Import orangedenv/config instead of orangedenv (Note: you do not need to call orangedenv.config() and must pass options via the command line or environment variables with this approach)
    3. Create a separate file that will execute config first as outlined in this comment on #133

    Contributing Guide


    Change Log


    Who's using orangedenv?

    These npm modules depend on it.

    Projects that expand it often use the keyword "orangedenv" on npm.


    npm i orangedenv

    DownloadsWeekly Downloads






    Unpacked Size

    24.4 kB

    Total Files


    Last publish


    • oranged