Kristiyan Kostadinov e30e61b789 fix(compiler-cli): avoid allocating an object for signals in production mode ...

Currently when the signal debug name transform sees something like `const foo = signal(0);`, it transforms the signal into `signal(0, {...(ngDevMode ? { debugName: 'foo' } : {})})`. After minification this becomes `signal(0, {})` which will allocate memory for the empty object literal.

These changes rework the logic to produce `signal(0, ...(ngDevMode ? [{ debugName: 'foo' }] : []))` which will be fully tree shaken away to `signal(0)`.

2025-12-02 15:06:51 +01:00

..

linker

refactor(compiler): remove unused code

2025-11-11 10:04:29 -08:00

private

Revert "refactor(compiler-cli): remove deep imports from compiler-cli (#64732)"

2025-11-06 13:09:01 -08:00

src

fix(compiler-cli): avoid allocating an object for signals in production mode

2025-12-02 15:06:51 +01:00

test

fix(compiler-cli): avoid allocating an object for signals in production mode

2025-12-02 15:06:51 +01:00

BUILD.bazel

Revert "refactor(compiler-cli): remove deep imports from compiler-cli (#64732)"

2025-11-06 13:09:01 -08:00

esbuild.config.js

build: use esbuild from aspect rules (#62568)

2025-07-10 13:45:15 -07:00

index.ts

refactor(compiler-cli): Remove deep imports of compiler-cli in angular/core

2025-10-28 15:58:56 +01:00

package.json

build: update dependency chokidar to v5

2025-12-02 12:11:10 +01:00

tsconfig-test.json

build: prepare for compiler-cli to be using ts_project (#61181)

2025-05-09 15:59:46 +00:00

tsconfig.json

build: prepare for compiler-cli to be using ts_project (#61181)

2025-05-09 15:59:46 +00:00