CODEWITHSUNDEEP
javascriptangularangular6
Daniel Oram
Daniel Oram

Reputation: 8411

Angular - process is not defined when trying to serve application

I am getting the following error when I try to serve my angular 6 application using cosmicjs:

Uncaught ReferenceError: process is not defined
    at Object../node_modules/cosmicjs/dist/index.js (index.js:6)
    at __webpack_require__ (bootstrap:81)
    at Object../src/app/app.component.ts (main.js:94)
    at __webpack_require__ (bootstrap:81)
    at Object../src/app/app.module.ts (app.component.ts:9)
    at __webpack_require__ (bootstrap:81)
    at Object../src/main.ts (environment.ts:18)
    at __webpack_require__ (bootstrap:81)
    at Object.0 (main.ts:12)
    at __webpack_require__ (bootstrap:81)

My latest theory is something to do with the process.env property being undefined.

I'm following this tutorial here

and my exact code can be found here

The tutorial seems to be using an older version of angular that uses .angular-cli.json instead of the new angular.json and I think this is part of the issue in trying to specify the environment variables.

Upvotes: 37

Views: 55268

Answers (8)

Davide Carpini
Davide Carpini

Reputation: 1711

if you need to deploy Angular 6 with serve:

polyfills.ts:

(window as any).global = window;
global.Buffer = global.Buffer || require('buffer').Buffer;
(window as any).process = {
    env: { DEBUG: undefined },
    version: '', // to avoid undefined.slice error
};

Upvotes: 0

c_froehlich
c_froehlich

Reputation: 1575

I had the same issue "out of a sudden" in an Angular 14 app.

It turned out I actually introduced it by myself: I forgot to remove a call to inspect (from Nodes util package) in a service class. Removing the call to inspect did the trick for me.

I added the call to inspect while debugging Jasmine unit tests. Running unit tests in Jasmine executes the code in Node. This is why it works in that environment.

In inspect there is a line

   if ( process.env.DEBUG )

Since process is not globally defined in the browser, execution of this line fails when running as Angular app.

This type of error is not restricted to util.inspect but will happen with any core module from Node running in the browser and accessing internally process.env.

Since the internal implementation of the core modules may vary from Node version to Node version, using core modules from Node puts the risk to you application that updating Node on the machine where the deployment build happens can break your application.

"path" is a another candidate that comes to my mind.

Upvotes: 1

Gowtham Gowda
Gowtham Gowda

Reputation: 2036

<script>
    if (global === undefined || process === undefined) {
      var global = window;
      window['process'] = {
        env: { DEBUG: undefined },
      };
    }
</script>

Upvotes: -1

Daniel Danielecki
Daniel Danielecki

Reputation: 10522

As long as you are not satisfied with putting some random logic into polyfills.ts and looking for a way to actually access the process.env in your Angular application please find below solution.

Change your "builder": "@angular-devkit/build-angular:dev-server" to "builder": "@angular-builders/custom-webpack:dev-server" in angular.json.

Upvotes: 3

buster95
buster95

Reputation: 710

To fix the problem, I added the following lines to 'polyfills.ts' file, 

(window as any).global = window;
global.Buffer = global.Buffer || require('buffer').Buffer;
global.process = require('process');

Upvotes: 31

Gurjeet singh
Gurjeet singh

Reputation: 181

This is an incompatibility with Angular 6. They removed support (shim) of process and global variables in browser.

Adding the following before your closing into your index.html will remove the error.

<script>
  var global = global || window;
  var Buffer = Buffer || [];
  var process = process || {
    env: { DEBUG: undefined },
    version: []
  };
</script>

Upvotes: 11

A T
A T

Reputation: 13826

In polyfill.ts, add this line:

(window as any).process = {
  env: { DEBUG: undefined },
};

Reference: https://github.com/algolia/algoliasearch-client-javascript/issues/691

Or npm i -S process, then add this to polyfill.ts:

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

Upvotes: 81

Daniel Habenicht
Daniel Habenicht

Reputation: 2243

This is an incompatibility with Angular v6. They removed support (shim) of process and global variables in browser.

I suggest you to use Angular 5, till cosmic.js fixes the error. Maybe you can even open an issue for it.

Upvotes: 10

Related Questions