Setting CI=true causes Angular 20 builds to fail with exit code -1073740940 on Windows

[myronu]

Which @angular/* package(s) are the source of the bug?

compiler-cli

Is this a regression?

Yes

Description

We recently upgraded our application from Angular 19 to 20. When we run a build on our Windows Jenkins server, our angular library fails to build and npm exits with error "-1073740940". When we run local it builds as expected.

I have tracked this down to Jenkins automatically setting the environment variable "CI" to true. I can reproduce the same error by setting the environment variable CI to true. I have yet to see the same error with CI not set or set to false.

I have tried multiple versions of both Node (21.9.5, 22.20.0) and NPM (10.9.3, 11.6.2) and get the same behavior.

Please provide a link to a minimal reproduction of the bug

No response

Please provide the exception or error you saw

npm verbose os Windows_NT 10.0.26100
npm verbose node v22.20.0
npm verbose npm  v11.6.2
npm verbose exit -1073740940
npm verbose code -1073740940

Please provide the environment you discovered this bug in (run ng version)

Anything else?

No response

[alan-agius4]

Setting the environment variable CI to true in ng-packagr disables caching.

The error code -1073740940 is not a standard Node.js or JavaScript error. It's typically a Windows OS exit code indicating the process terminated, often due to a low-level issue like heap memory corruption.

We are unable to replicate this issue as CI: true is also used for ng-packagr's tests, these specific tests pass successfully on both Linux and Windows environments.