unit-test builder (Vitest, 22.2.0 OXC linker): ReferenceError on class referenced by name before its own declaration in a partially-compiled npm library
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 48/100
- Tipo de issue
- Bug
- Clareza
- Razoavelmente clara
- Status de atividade
- Ativa
- Stack de tecnologia
- angular, typescript
- Domínio
- build-system, testing-qa
Direção de pesquisa
Start with the @angular/build:unit-test builder and the emitted node_modules/@openng/optimus-ui/fesm2022/openng-optimus-ui-cascadeselect.mjs file, focusing on the OXC-based Angular linker handling of the partial declarations for CascadeSelectSub and CascadeSelect. Compare this path with the classic Karma pipeline. Done means the affected import graph loads without the ReferenceError and the unit-test suite reports its tests instead of zero.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Command
test
Is this a regression?
Not sure — this may be a regression introduced by the linker rewrite in 22.2.0 ("migrate Angular Linker to oxc-parser and magic-string"), since I have not tested this with 22.1.x.
The previous version in which this bug was not present was
No response
Description
When running ng test with the @angular/build:unit-test builder (Vitest runner) on Angular CLI / @angular/build 22.2.0, several test files fail to load at all (0 tests reported, whole suite crashes) with:
ReferenceError: Cannot access 'CascadeSelect' before initialization
at CascadeSelectSub.<static_initializer> node_modules/@openng/src/cascadeselect/cascadeselect.ts:131:30
I traced this to the actual shipped file (the path above is a sourcemap reference, not a real file on disk):
node_modules/@openng/optimus-ui/fesm2022/openng-optimus-ui-cascadeselect.mjs
In that file, CascadeSelectSub is declared at line 176, and its static Ivy partial declaration at line 274 includes:
static ɵfac = i0.ɵɵngDeclareFactory({ ..., type: CascadeSelectSub, deps: [{ token: CascadeSelect }], target: i0.ɵɵFactoryTarget.Component });
CascadeSelect (the referenced class) is not declared until line 452, further down in the same file. Since this is emitted as a literal class declaration (temporal dead zone applies), referencing the identifier CascadeSelect before its declaration executes throws a ReferenceError — unless the Angular linker processes this partial-compilation output (ɵɵngDeclareFactory, ɵɵngDeclareComponent) into a fully-linked form first, which is presumably not order-sensitive.
This same package builds and tests fine under the classic Karma + @angular-devkit/build-angular pipeline, which suggests the linker is applied correctly there but not (or not correctly) for this specific cross-class-reference pattern under the unit-test builder in 22.2.0.
Minimal Reproduction
I don't have an isolated reproduction yet, but you've provided the full trace and the exact line of the affected packet.
Exception or Error
ReferenceError: Cannot access 'CascadeSelect' before initialization
❯ CascadeSelectSub.<static_initializer> node_modules/@openng/src/cascadeselect/cascadeselect.ts:131:30
❯ node_modules/@openng/src/cascadeselect/cascadeselect.ts:131:39
(Note: the path shown is from the package's sourcemap; the real file evaluated is `node_modules/@openng/optimus-ui/fesm2022/openng-optimus-ui-cascadeselect.mjs`.)
Your Environment
Angular CLI: 22.2.0
@angular/build: 22.2.0
Vitest: 5.0.2
Node: v24.21.0
OS: Windows
Anything else relevant?
- The affected npm package is
@openng/optimus-ui(latest version at time of reporting). - The broken class is
CascadeSelect/CascadeSelectSub, distributed in Ivy partial-compilation format (ɵɵngDeclareComponent,ɵɵngDeclareFactory). CascadeSelectSubis declared earlier in the file thanCascadeSelect, and its factory'sdepsarray referencesCascadeSelectby identifier without going throughforwardRef.- This surfaced right after upgrading to 22.2.0, which per the changelog migrated the Angular Linker to oxc-parser/magic-string and included several linker-related fixes in the same release (syntax corruption, parenthesized expressions, source mapping). This may be an edge case not yet covered by the new OXC-based linker implementation.
- Affects every test file whose import graph pulls in this component (via a shared header/footer module), causing the whole suite (not just one test) to fail to load — reported as "(0 test)" by Vitest.
- Linguagem predominante
- TypeScript
- Estrelas
- 27k
- Forks
- 11.8k
- Merge médio
- 21h 31min
- PRs com merge (30d)
- 168
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de angular/angular-cli
-
area: @angular/build gemini-triaged
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 74/100
angular/angular-cli#33955 ·
Mantenedores costumam responder em até 1 dia
-
area: @angular/cli gemini-triaged
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
angular/angular-cli#33055 · 1 comentário · 3 reações ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 52/100
angular/angular-cli#34207 ·
Mantenedores costumam responder em até 1 dia
-
library builder: tslib is not added to the output package.jsonTalvez já em andamento @alan-agius4 assumiu há 10 dias. Abertaangular/build:library area: @angular/build gemini-triaged
angular/angular-cli#34131 · 1 responsável ·
Mantenedores costumam responder em até 1 dia
-
library builder: a name re-exported through two "export *" paths is dropped from the bundleTalvez já em andamento @alan-agius4 assumiu há 10 dias. Abertaangular/build:library area: @angular/build gemini-triaged
angular/angular-cli#34130 · 1 responsável ·
Mantenedores costumam responder em até 1 dia
Todas as issues de angular/angular-cli
Issues semelhantes
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 78/100
lichess-org/api#678 ·
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 84/100
PostHog/posthog.com#20628 ·
Mantenedores costumam responder em até 1 dia
-
bug status:Needs Triage
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 92/100
jupyterlab/jupyterlab#19964 ·
Mantenedores costumam responder em até 1 dia
-
bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
agentscope-ai/QwenPaw#8064 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
area: notebooks-jupyter bug theme: new notebook frontend
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 88/100
posit-dev/positron#16347 · 1 comentário ·
Mantenedores costumam responder em até 1 dia