Skip to content

Divergences from ngtsc found by running Angular's ngtsc emit specs (non-functional) #623

Open

Description

@edbzn

Summary

I ran Angular v22.0.0's own packages/compiler-cli/test/ngtsc/*_spec.ts emit tests against oxc main (04cb3b2, angularVersion 22.0.0). For each test, driveMain() was replaced with transformAngularFileSync. Of 527 tests that assert on emitted JS, 254 pass. This issue lists the remaining divergences that aren't runtime bugs, so they're tracked in one place. Items marked (known) are already in e2e/compare/fixtures/known-differences.ts.

Dev-mode only

Divergence ngtsc spec
Signal APIs (signal, computed, input, model, linkedSignal, resource, httpResource, queries…) get no debugName (known) debug_transform_spec.ts (72 tests)
ɵɵattachSourceLocations(...) never emitted (template source locations for DevTools) attach_source_location_spec.ts (4)
forbidOrphanRendering: true missing from ɵsetClassDebugInfo when forbidOrphanComponents is set (no equivalent option) ngtsc_spec.ts "should set forbidOrphanRendering debug info…" (2)
setClassMetadata uses type: i1.KeyCodes for a const enum ctor param, where ngtsc uses type: undefined ngtsc_spec.ts "should use undefined in setClassMetadata for const enums"

Bundle size

Divergence ngtsc spec
ɵɵsetNgModuleScope isn't guarded by ngJitMode (known, intentional) scope_spec.ts, ngtsc_spec.ts "should compile NgModules without errors"
ɵɵdefineInjector({ imports }) keeps standalone directives and pipes (and NgModule-exported directives) that ngtsc filters out standalone_spec.ts "optimizations …" (4), ngtsc_spec.ts "InjectorDef emit optimizations…" (2), "should filter out directives and pipes from module exports in the injector def"
schemas: [...] is emitted in ɵcmp/ɵmod; ngtsc drops it standalone_spec.ts "…with schema support", ngtsc_spec.ts "should not include schemas in component and module defs"
Query predicates are inlined (ɵɵviewQuery(["test1"], 5)) instead of pooled constants (const _c0 = ["test1"]) ngtsc_spec.ts "should generate queries for directives"
Identical inline styles across components in one file aren't shared through a _c0 constant ngtsc_spec.ts "inline resources should share same styles…"

Different output, same runtime behaviour

  • Dependencies use ɵɵgetComponentDepsFactory(Cmp, imports) instead of the resolved list (known). This also accounts for the setComponentScope cycle-detection tests.
  • @defer loaders are inline arrows in ɵɵdefer(i, j, () => [import(...)]). ngtsc emits a named Cmp_Defer_N_DepsFn const that also lists eagerly available local deps, and () => [CmpA] when nothing is lazy. (defer_spec.ts, ~20 tests)
  • Constructors that can't be injected compile to new C(ɵɵinvalidFactoryDep(n)), where ngtsc emits ɵɵinvalidFactory(). Both throw on instantiation, with different messages. (ngtsc_spec.ts "compiling invalid @Injectables/@Directives…", local_compilation_spec.ts "should generate invalid factory…", 16 tests)
  • Import shape:
    • named imports are kept, where ngtsc re-emits import * as i1;
    • no local-compilation side-effect imports (import "./dep");
    • ModuleWithProviders constants aren't unwrapped (imports: [mwp] vs [i1.DepModule]);
    • default-imported tokens are emitted as i1.default.

Not applicable to oxc (for completeness)

.d.ts assertions in full mode, flat module index, Bazel/g3 alias re-exports (ɵngExportɵ…, _useHostForImportAndAliasGeneration), Closure annotations, compileNonExportedClasses, supportTestBed/supportJitMode: false.


Functional bugs found by the same run are filed separately; links in a comment below.

Activity

  1. edbzn commented on Oct 25, 2026

    @edbzn
    ContributorAuthor

    Functional bugs found by the same run, each with a fix:

  2. Brooooooklyn commented on Oct 28, 2026

    @Brooooooklyn
    Member

    I re-checked every item on main 5780233 against ngtsc 22.2.3, in full and partial mode.

    Fixed by an open PR

    Item PR
    ɵɵinvalidFactoryDep(n) instead of ɵɵinvalidFactory() / deps: "invalid" #657
    schemas in ɵmod (ɵcmp already matched) #657
    Query predicates inlined, in directives (components already pooled) #657
    Default-imported token emitted as i1.default (this one came from oxc, not ngtsc) #657
    @Inject(TOKEN) rewritten to i1.TOKEN (left over from the import-shape item) #657
    Signal APIs get no debugName (known) #658
    @defer loaders inline instead of Cmp_Defer_N_DepsFn, one shared fn for all blocks #659
    Identical inline styles not shared via _c0 (only strings of 50+ chars, as in ngtsc), and query predicates not shared across classes #660

    Already matches ngtsc on main

    • Named imports vs import * as i1: ctor types, metadata, host directives and deps all match now.
    • Short identical styles: ngtsc inlines them too.
    • Local-compilation side-effect imports (import "./dep"): ngtsc emits them only in experimental-local with generateExtraImportsInLocalMode.

    Still open

    Item Why
    ɵɵattachSourceLocations Needs an enableTemplateSourceLocations option. It is off by default in ngtsc, and the Angular CLI never sets it.
    forbidOrphanRendering Needs a forbidOrphanComponents option. The Angular CLI doesn't set it either.
    const enum param type in setClassMetadata Can be done for a same-file const enum. An imported one needs type info from another file.
    ɵɵdefineInjector({ imports }) filtering Needs to know, from another file, whether each import is a directive, pipe or NgModule.
    ModuleWithProviders constants not unwrapped Same: needs the other file's types.
    ɵɵgetComponentDepsFactory (known) Intentional, because oxc compiles one file at a time.
    ɵɵsetNgModuleScope without the ngJitMode guard (known) Intentional: ɵɵgetComponentDepsFactory reads the scope at runtime.

    Runtime bugs found by the same re-check

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions