Getting error while running "ng serve" for my first angular application

Question

Message&trace:

Generating browser application bundles (phase: building)...(node:5312) UnhandledPromiseRejectionWarning: TypeError: MessagePort was found in message but not listed in transferList
    at new Worker (internal/worker.js:170:17)
    at SassWorkerImplementation.createWorker (C:\Users\shail\iacademiaApp1\node_modules\@angular-devkit\build-angular\src\sass\sass-service.js:96:24)
    at SassWorkerImplementation.render (C:\Users\shail\iacademiaApp1\node_modules\@angular-devkit\build-angular\src\sass\sass-service.js:62:40)
    at Object.loader (C:\Users\shail\iacademiaApp1\node_modules\sass-loader\dist\index.js:46:3)
(node:5312) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:5312) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:5312) UnhandledPromiseRejectionWarning: TypeError: MessagePort was found in message but not listed in transferList
    at new Worker (internal/worker.js:170:17)
    at SassWorkerImplementation.createWorker (C:\Users\shail\iacademiaApp1\node_modules\@angular-devkit\build-angular\src\sass\sass-service.js:96:24)
    at SassWorkerImplementation.render (C:\Users\shail\iacademiaApp1\node_modules\@angular-devkit\build-angular\src\sass\sass-service.js:62:40)
    at Object.loader (C:\Users\shail\iacademiaApp1\node_modules\sass-loader\dist\index.js:46:3)
(node:5312) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
/ Generating browser application bundles (phase: building)...

Explain your scenario properly.

Pal Singh
– Pal Singh

2021-05-20 08:46:13 +00:00
Commented May 20, 2021 at 8:46 — Pal Singh
– Pal Singh, Commented May 20, 2021 at 8:46

Mikkel Christensen · Accepted Answer · 2021-05-23 09:16:06Z

13

The latest version of the Angular CLI (12.0.1) does not support Node below version 12.20.

Solution

Update your version of Node to the latest stable version

You should pick the version marked LTS, which at the time of writing is in the 14.x.x range.

Workaround

Only do this if you for some reason are completely unable to update your Node version

Add node-sass to your project devDependencies until you are able to update your version of node.

npm i -save-dev node-sass

yarn add -D node-sass

You should be careful with this workaround, as node-sass is going to be deprecated soon.

edited May 23, 2021 at 9:16

answered May 20, 2021 at 11:42

Mikkel Christensen

2,8571 gold badge16 silver badges23 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

BruneX Over a year ago

In my case this isn't working, I'm currently using node 14.17.0 LTS and I'm experiencing the same error.

Kashyap · Accepted Answer · 2021-05-20 09:00:05Z

2

Please try this:

ng update @angular/cli

npm install

answered May 20, 2021 at 9:00

Kashyap

663 bronze badges

Collectives™ on Stack Overflow

Getting error while running "ng serve" for my first angular application

2 Answers 2

Solution

Workaround

1 Comment

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Solution

Workaround

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related