Use Node Environment Variables in Client-side Apps with Webpack

January 12, 2019 • 9 min read

CI / CDDevOpsJavaScriptNode.jsReactWebpack
Taylor Sturtz

Taylor Sturtz

Software Developer

GitHub • Twitter

For applications that are developed locally and deployed to multiple server environments (staging, production, etc.), environment variables are essential. Common uses are conditionally executing code based on environment flags or storing base URLs for APIs with matching environments. You may also want to store specific values in environment variables for security reasons — this is critical in server-side code, but may also be useful on the client-side if you do not want to commit certain values to source code, for example. But of course, never store secret/sensitive information in client-side code.

We’ll set up your webpack configuration to parse environment variables as globals in your app and go over the steps to implement a .env file to define environment variables locally. Then we’ll briefly touch on how you might implement environment variables on the server.

The following assumes some stuff

You have Node.js and a package manager such as npm or yarn installed.

You’re using webpack (with or without React).

You can of course define environment variables in Angular but the process is a bit different than what is explained below. You can define environment variables in Vue as well and even though Vue uses webpack — it’s very frameworky about how to do things.

You’re are able to manage your server/deployment configuration.

Whether you’re building your app directly on the server, or using a CI/CD service (such as Netlify, Heroku, Travis CI, Circle CI, or GitLab), you’ll need to know how to set your environment variables per environment.

👍 Let’s get into it..

Local environment variables

Define your variables in a .env file

  1. Create a .env file in your project’s root directory.

    touch .env
  2. Add a .env entry to your project’s .gitignore file.

    # FILE: /.gitignore.env # Environment variables for local development.
  3. Add your environment variables in your .env file as key / value pairs, like so:

    # FILE: /.env# Individual variables
    # If you prefer to use just one environment variable in your config you can
    # define a JSON object that you can then parse in your webpack config.
    # NOTE: For this to work, the JSON must be formatted this way (inline).
    CONFIG_JSON={"server_env": "local", "urls": {"my_api_base_url": ""}}

Since you will not commit your .env file to version control, you may want to create another file (which you will commit) called .env.example with dummy values just to indicate which variables your application expects. For example:

# FILE: /.env.exampleSERVER_ENV=(environment_here)
CONFIG_JSON={"server_env": "environment_here", "urls": {"my_api_base_url": "url_here"}}

When naming your variables, try to be explicit so they don’t conflict with other Node variables (like CI built-in variables, ie: Travis CI, Circle CI, and GitLab CI).

⚠️ ATTN: create-react-app and Gatsby users!

The above should work except for one caveat: variables defined in your .env file must be prefixed with REACT_APP_ or GATSBY_ in order to use them in your app.

See the create-react-app docs or the gatsby docs for more info.

If you are working with other developers you’ll need to share your .env file and make sure changes are updated everywhere.

Use the variables defined in your .env in your application

  1. Install the dotenv node package

    # Install with npm
    npm i dotenv
    # or with yarn if that's your thing
    yarn add dotenv
  2. Paste this bit of code near the top of your webpack config. The isCiBuild bit prevents webpack from unnecessarily requiring dotenv in CI environments (be sure to check that CI is a built in variable in your service).

    // FILE: /webpack.config.js// If we're using Travis CI for example, we can check if webpack is building our app in a CI environment.
    const isCiBuild = !!process.env.CI
    if(!isCiBuild) {
  3. Add DefinePlugin to your webpack config. If you’re not sure how to add plugins to your webpack config, see the Plugins webpack docs. This example shows how to assign individual environment variables as well as parsed JSON variables.

    // FILE: /webpack.config.js{
      // ... other webpack config stuff
      plugins: [
        // ... other plugins if you have any
        new webpack.DefinePlugin({
          // ... any other global vars
          VERSION: JSON.stringify('1.2.3'), // just an example of a global variable you could add
          // pull in your individual .env vars      SERVER_ENV: JSON.stringify(process.env.SERVER_ENV),      MY_API_BASE_URL: JSON.stringify(process.env.MY_API_BASE_URL),      // OR parse your JSON vars if you used this method      SERVER_ENV: JSON.stringify(JSON.parse(process.env.CONFIG_JSON).server_env),      MY_API_BASE_URL: JSON.stringify(JSON.parse(process.env.CONFIG_JSON).urls.my_api_base_url),    }),
  4. Use your new variables in your application.

    console.log(`version: ${VERSION}`) // '1.2.3'
    console.log(`version: ${SERVER_ENV}`) // 'local'
    if (SERVER_ENV !== 'production') {
      // this code will NOT run on production
    } else {
      // this code will run on production

    If you’re not familiar with the syntax below, check out my other post about async/await.

    const getUsers = async () => {
      try {
        const response = await fetch(`${MY_API_BASE_URL}/users`) // transpiles to fetch('')    const json = await response.json()    return json
      } catch (err) {

    If all went well implementing the steps above, we have now configured webpack to use environment variables as global application variables in our webpack build! 🎉

Works on my machine!

Bonus - linter globals

You can add your global variables to your .eslintrc or .jshintrc config file which will allow you to use your globals freely without your linters yelling at you:

// FILE: /.eslintrc or /.jshintrc{
  // ...
  "globals": {
    "VERSION": true,
    "SERVER_ENV": true,
    "MY_API_BASE_URL": true,

You can achieve the same thing on a per-file basis if you put a comment at the top of your file like this:


Server environment variables

There are a number of ways to set environment variables and your configuration is going to be unique to your project.

Whichever method you chose just make sure that environment variables are set before running the webpack build script because webpack will transpile those values into your JS bundle which can then be deployed.

Directly on the server

You can install Node.js on each server and set your environment variables via the process global variable like so:

process.env.SERVER_ENV = 'production'

or install the dotenv package:

# Install with npm
npm i dotenv
# or with yarn if that's your thing
yarn add dotenv

and manually maintain a .env file on each server.

In your CI service interface

In the project settings of your CI service you’ll find a place to add environment variables. For static values this is a great place to store and manage them.

Travis CI Circle CI GitLab CI
Travis CI Environment Variables UI Circle CI Environment Variables UI GitLab CI Environment Variables UI

GitLab is unique in that it allows for specifying variables for each environment (staging, production, etc) in the UI and then specify which environment to use for each job in a configuration file.

In a CI config file

CI services all allow you to write YAML configuration files that provide deployment instructions. You will need to define jobs to run that set environment variables based on which branch you are pushing to and which server you are deploying to.

Use Docker/Kubernetes

I don't know

…yet 😉

🎉 That’s it!

Now that webpack can understand your server configuration and your new local .env file, you can use environment variables in your app and easily manage them locally and on your server.

We did it!

For more info about setting environment variables in other types of client-side apps or to configure CI deployment steps, check out the resources below.

Additional resources