ng update @angular/core@19 @angular/cli@19 Failed.

[oritpersik]

Command

update

Is this a regression?

• Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

18

Description

I'm running NODE_OPTIONS="--max-old-space-size=8192" ng update @angular/core@19 @angular/cli@19
but the command fails with
❯ Update '@angular/ssr' import paths to use the new '/node' entry point when 'CommonEngine' is detected.
✖ Migration failed: Map maximum size exceeded
See "/tmp/ng-pCWODy/angular-errors.log" for further details

Minimal Reproduction

Node version: v22.13.1
My projects is not using ssr at all. how can i skip this migration ?

This is the tmp file with the error:

Exception or Error

![Image](https://github.com/user-attachments/assets/e833fe0f-a9b5-4fcd-b81e-8bc1a63a557f)
this is the tmp file with the error:

Your Environment

Angular CLI: 19.1.5
Node: 22.13.1
Package Manager: npm 10.9.2
OS: linux x64

Angular: 19.1.4
... animations, common, compiler, compiler-cli, core, elements
... forms, language-service, localize, platform-browser
... platform-browser-dynamic, platform-server, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.901.13
@angular-devkit/build-angular   19.1.5
@angular-devkit/core            9.1.13
@angular-devkit/schematics      19.1.5
@angular/cdk                    18.2.14
@angular/cli                    19.1.5
@angular/material               18.2.14
@schematics/angular             19.1.5
ng-packagr                      19.1.2
rxjs                            7.8.1
typescript                      5.5.4
zone.js                         0.15.0

Anything else relevant?

I must upgrade our angular product to angular 19, please help me to resolve this issue as soon as possible.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}