For namespaced environment variables (more secure) check lines 10 - 28 on this StackBlitz page.

With dotenv package:

1. Install dotenv:

   yarn add -D dotenv or npm i -D dotenv

2. Add .env file in your project root with the required variables:

   NODE_ENV=developmentapiKey=w23io222929kdjfkdomain=example.domain.org

3. Define these variables with webpack.DefinePlugin:

   // webpack.config.jsconst webpack = require('webpack')const dotenv = require('dotenv')// this will update the process.env with environment variables in .env filedotenv.config();module.exports = {//...plugins: [// ...new webpack.DefinePlugin({'process.env': JSON.stringify(process.env)})// ...]//...}

4. Access environment variables in your source code:

   // src/index.jsalert(process.env.NODE_ENV)alert(process.env.apiKey)

StackBlitz example: https://stackblitz.com/edit/node-kdfi4z?file=index.js

This is how i resolved the

ReferenceError: process is not defined

error with Webpack 5

1. npm i --save-dev process

2. Delete the "node_modules" folder

3. Add const webpack = require('webpack'); at the top of your config file

4. In your webpack config file, plugin section, add below:

   plugins: [new webpack.ProvidePlugin({process: 'process/browser',}),

5. Also in the webpack add the alias like below:

   resolve: {alias: {process: "process/browser"},

6. Now do npm i

...and when you build your application the error will disappear.you can read about webpck migration [here]

You need to add a plugin to define your env (in webpack config):

 plugins: [new webpack.DefinePlugin({'process.env.NODE_ENV': JSON.stringify('development')})],

Webpack 5 removes the ability to access environment variables using the notation process.env.MY_ENV_VAR. I had this same problem because I was getting a Uncaught ReferenceError: process is not defined error in my browser console. From the documentation of porting from v4 to v5 of Webpack, they mention the following:

1. Before upgrading to v5, verify that you can easily do it

Try to set the following options in your webpack 4 configuration andcheck if build still works correctly.

module.exports = {// ...node: {Buffer: false,process: false}};

webpack 5 removes these options from the configuration schema and will always use false.

You have to remove these options again when upgrading yourconfiguration for webpack 5.

2. Handling env vars because process was removed

• Regarding Runtime Errors:
  • process is not defined.
    • webpack 5 does no longer include a polyfill for this Node.js variable. Avoid using it in the frontend code.
    • Want to support frontend and browser usage? Use the exports or imports package.json field to use different code depending on theenvironment.
      • Also use the browser field to support older bundlers,.
      • Alternative: Wrap code blocks with the typeof process checks. Note that this will have a negative impact on the bundle size.
    • Want to use environment variables with process.env.VARIABLE? You need to use the DefinePlugin or EnvironmentPlugin to define thesevariables in the configuration.
      • Consider using VARIABLE instead and make sure to check typeof VARIABLE !== 'undefined' too. process.env is Node.js specificand should be avoided in frontend code.

Therefore, given the above information, it is possible to use environment variables using one of the two plugins below.

const webpack = require("webpack");module.exports = {...plugins: [new webpack.DefinePlugin({"process.env.MY_ENV_VAR": JSON.stringify(process.env.MY_ENV_VAR)}),new webpack.EnvironmentPlugin(['MY_ENV_VAR']); // <--This is shorthand, does the same thing as the DefinePlugin],};

Then in your production code it's still feasable to refer to the environment variable in the same way, example:

console.log(process.env.MY_ENV_VAR);

However, as they said in the documentation included above, using process.env is NOT the recommended way since that is Node.js specific.

Webpack 5, the easiest solution for me...

npm install dotenv-webpack --save-dev

// webpack.config.jsconst Dotenv = require('dotenv-webpack');module.exports = {...plugins: [new Dotenv()]...};

To avoid error like denoted in the question I had have provide in webpack.config.js the next configuration (note defining variable level: process.env):

new webpack.DefinePlugin({"process.env": JSON.stringify(process.env)})

Now it works fine. I'm using webpack 5.30.0, Vue 2.6.12 and vuelidate 0.7.6.

Error I had before in browser console:

Uncaught ReferenceError: process is not definedat Object.../node_modules/vuelidate/lib/withParams.js

It is not good thing, that browser client library "vuelidate" requires Node.js specific env variables. Confused build and runtime areas in library.

Works for me to allow reading env variables inside React, using "webpack": "^5.1.3",

webpack.config.js

const webpackConfig = {plugins: [new webpack.ProvidePlugin({process: 'process/browser',}),new webpack.DefinePlugin({'process.env': JSON.stringify(process.env)})],};

:)

Having dotenv-webpack/dotenv in your webpack and still doesn't work on Angular? Most probably you're trying to access process.env when running the Angular app on the browser (without Angular Universal), e.g. by ng serve.

Run npm i -S process and then in polyfills.ts paste the code below

import * as process from "process";window["process"] = process;

Alternatively, if that's not the case and you're looking for webpack to obtain environmental variables then (I don't know why no one suggested yet) dotenv-webpack is the simplest one.

const dotenv = require("dotenv-webpack");const webpackConfig = {plugins: [new dotenv()]};module.exports = webpackConfig; // Export all custom Webpack configs.

Of course you need to have them defined in .env file at the root of your project.

If it is useful for someone:

I tried almost every approach in this thread unsuccessfully.When I went deeper into the problem I realized that what was causing this error on my application was the usage of assert lib:

import * as assert from 'assert';... assert(myVariable !== undefined, "Try to update undefined myVariable ");

BTW: I'm using Angular@~11.2.7

My problem was process is undefined error on internet explorer 11 using webpack 5.

This is how I solved my problem with process.env.MY_ENV_VAR thanks to @ArianPopalyar.
Ref. Answer

In addition to her solution, I added EnvironmentPlugin in webpack.config.js:

...plugins: [new webpack.ProvidePlugin({process: 'process/browser'}),new webpack.EnvironmentPlugin({PATH_MODERN: 'dist/modern/domready.min.js',PATH_LEGACY: 'dist/legacy/domready.min.js',DEBUG: false}),...]

and using it in index.js

if (process.env.PATH_LEGACY) {// ...}

For anyone still struggling with this here's something you could try:

Replace the process/browser with process or process/browser.js

 new webpack.ProvidePlugin({process: 'process'})

With webpack 5 and ES6 modules I think there's some difficulty in package resolution here, which is why we need a better path for the process.

Otherwise try including this in your webpack.config:

 resolve: {fallback: {'process/browser': false,}},

This can work to overcome the error, but not sure if it doesn't actually break the place where it's being used. In my case the first suggestion worked out.

Easy way: prepend the variable "NODE_ENV" when you call webpack i.e. NODE_ENV=production webpack --watch