dotenv-webpack

A secure webpack plugin that supports dotenv and other environment variables and only exposes what you choose and use.

Installation

Include the package locally in your repository.

npm install dotenv-webpack --save-dev

Description

dotenv-webpack wraps dotenv and Webpack.DefinePlugin. As such, it does a text replace in the resulting bundle for any instances of process.env.

Your .env files can include sensitive information. Because of this,dotenv-webpack will only expose environment variables that are explicitly referenced in your code to your final bundle.

Interested in taking your environments to the next level? Check out the Dotenv Organization.

Usage

The plugin can be installed with little-to-no configuration needed. Once installed, you can access the variables within your code using process.env as you would with dotenv.

The example below shows a standard use-case.

Create a .env file

1// .env
2DB_HOST=127.0.0.1
3DB_PASS=foobar
4S3_API=mysecretkey
5

Add it to your Webpack config file

1// webpack.config.js
2const Dotenv = require('dotenv-webpack');
3
4module.exports = {
5  ...
6  plugins: [
7    new Dotenv()
8  ]
9  ...
10};

Use in your code

1// file1.js
2console.log(process.env.DB_HOST);
3// '127.0.0.1'

Resulting bundle

1// bundle.js
2console.log('127.0.0.1');

Note: the .env values for DB_PASS and S3_API are NOT present in our bundle, as they were never referenced (as process.env.[VAR_NAME]) in the code.

How Secure?

By allowing you to define exactly where you are loading environment variables from and bundling only variables in your project that are explicitly referenced in your code, you can be sure that only what you need is included and you do not accidentally leak anything sensitive.

Recommended

Add .env to your .gitignore file

Limitations

Due to the fact that we use webpack.DefinePlugin under the hood, we cannot support destructing as that breaks how this plugin is meant to be used. Because of this, please reference your variables without destructing. For more information about this, please review the issue here.

process.env stubbing / replacing

process.env is not polyfilled in Webpack 5+, leading to errors in environments where process is null (browsers).

We automatically replace any remaining process.envs in these environments with "MISSING_ENV_VAR" to avoid these errors.

When the prefix option is set, process.envs will not be stubbed.

If you are running into issues where you or another package you use interfaces with process.env, it might be best to set ignoreStub: true and make sure you always reference variables that exist within your code (See this issue for more information).

Properties

Use the following properties to configure your instance.

• path ('./.env') - The path to your environment variables. This same path applies to the .env.example and .env.defaults files. Read more here.
• safe (false) - If true, load '.env.example' to verify the '.env' variables are all set. Can also be a string to a different file.
• allowEmptyValues (false) - Whether to allow empty strings in safe mode. If false, will throw an error if any env variables are empty (but only if safe mode is enabled).
• systemvars (false) - Set to true if you would rather load all system variables as well (useful for CI purposes).
• silent (false) - If true, all warnings will be suppressed.
• expand (false) - Allows your variables to be "expanded" for reusability within your .env file.
• defaults (false) - Adds support for dotenv-defaults. If set to true, uses ./.env.defaults. If a string, uses that location for a defaults file. Read more at npm.
• ignoreStub (false) - Override the automatic check whether to stub process.env. Read more here.
• prefix ('process.env.') - The prefix to use before the name of your env variables.

The following example shows how to set any/all arguments.

1module.exports = {
2  ...
3  plugins: [
4    new Dotenv({
5      path: './some.other.env', // load this now instead of the ones in '.env'
6      safe: true, // load '.env.example' to verify the '.env' variables are all set. Can also be a string to a different file.
7      allowEmptyValues: true, // allow empty variables (e.g. `FOO=`) (treat it as empty string, rather than missing)
8      systemvars: true, // load all the predefined 'process.env' variables which will trump anything local per dotenv specs.
9      silent: true, // hide any errors
10      defaults: false, // load '.env.defaults' as the default values if empty.
11      prefix: 'import.meta.env.' // reference your env variables as 'import.meta.env.ENV_VAR'.
12    })
13  ]
14  ...
15};

About path settings

As previously mentioned, it is possible to customize the path where the .env file is located as well as its filename from the plugin settings:

1module.exports = {
2  ...
3  plugins: [
4    new Dotenv({
5      path: './some.other.env',
6    })
7  ]
8  ...
9};

It is important to mention that this same path and filename will be used for the location of the .env.example and .env.defaults files if they are configured, this will only add the .example and .defaults suffixes respectively:

1module.exports = {
2  ...
3  plugins: [
4    new Dotenv({
5      path: '../../path/to/other.env',
6      safe: true, // load '../../path/to/other.env.example'
7      defaults: true, // load '../../path/to/other.env.defaults'
8    })
9  ]
10  ...
11};

This is especially useful when working with Monorepos where the same configuration can be shared within all sub-packages of the repository:

1.
2├── packages/
3│   ├── app/
4│   │   └── webpack.config.js # { path: '../../.env' }
5│   └── libs/
6│       └── webpack.config.js # { path: '../../.env' }
7├── .env
8├── .env.example
9└── .env.defaults

LICENSE

MIT