Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#623 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
28/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
angular, rust, typescript
Ambito
testing-qa

Direzione di ricerca

Start with the listed Angular ngtsc emit specs and compare their expected output with oxc’s transformAngularFileSync output; the issue groups divergences by dev mode, bundle size, and runtime behavior. Choose one divergence and trace the corresponding compiler path. Done means the selected case matches Angular’s output where required, or its behavior and rationale are documented.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Rust
Stelle
244
Fork
26
Merge medio
23h 41m
PR unite (30g)
106

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di voidzero-dev/oxc-angular-compiler

Tutte le issue di voidzero-dev/oxc-angular-compiler

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.