After update to Angular 8 CLI throws ".getColorDepth is not a function"

Question

A collegue of mine upgraded our project to angular 8. I pulled his branch and run npm install. On his branch everyhing works fine. I do now get the same error every time i run any "ng ..." command:

C:\xxx\party-ui\node_modules\@angular\cli\utilities\color.js:15
    process.stdout.getColorDepth() > 1;
                   ^

    TypeError: process.stdout.getColorDepth is not a function
        at Object.<anonymous> (C:\xxx\party-ui\node_modules\@angular\cli\utilities\color.js:15:20)
        at Module._compile (module.js:652:30)
        at Object.Module._extensions..js (module.js:663:10)
        at Module.load (module.js:565:32)
        at tryModuleLoad (module.js:505:12)
        at Function.Module._load (module.js:497:3)
        at Module.require (module.js:596:17)
        at require (internal/module.js:11:18)
        at Object.<anonymous> (C:\xxx\party-ui\node_modules\@angular\cli\models\analytics.js:18:17)
        at Module._compile (module.js:652:30)

I also tried to update npm and node (now having versions 10.16.0 and 6.9.0). Also removed the node_modules folder and run npm install after that. What can I do?

Answer 1

Look in the problematic file ./node_modules/@angular/cli/utilities/color.js. Notice a comment above the problematic line (15):

"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
/**
 * @license
 * Copyright Google Inc. All Rights Reserved.
 *
 * Use of this source code is governed by an MIT-style license that can be
 * found in the LICENSE file at https://angular.io/license
 */
 const colors = require("ansi-colors");
 exports.colors = colors;
 const tty_1 = require("tty");
 // Typings do not contain the function call (added in Node.js v9.9.0)
 exports.supportsColor = process.stdout instanceof tty_1.WriteStream &&
    process.stdout.getColorDepth() > 1;
 colors.enabled = exports.supportsColor;

Specifically:

// Typings do not contain the function call (added in Node.js v9.9.0)

Upgrading Node to a version no less than v9.9.0 fixes the problem.

but...

...choosing how to upgrade NodeJS is not necessairly straightforward. See How do I update Node.js?. Some popular answers are quite far down the page so it's worth scrolling through.