`@angular/build:unit-test` with Vitest test runner throws `Failed to import test file` error

Aperta
#31,993 6 commenti 30 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
52/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
angular, typescript

Direzione di ricerca

Inizia dall’analisi della gestione di providersFile del runner @angular/build:unit-test e del file init-testbed.js generato, quindi riproduci il problema usando il repository minimo collegato. Verifica la correzione eseguendo ng test con TestService che inietta Router e confermando che tutte le spec vengano importate e superino i test senza l’errore del compilatore JIT.

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

Descrizione

angular/build:unit-test area: @angular/build freq1: low severity3: broken type: bug/fix
Command

test

Is this a regression?
  • Yes, this behavior used to work in the previous version
The previous version in which this bug was not present was

No response

Description

Steps to reproduce:

  1. Create a TestService that will contain a single property router = inject(Router)
  2. Configure @angular/build:unit-test runner to include providersFile
  3. Export [TestService] from it
  4. Create a Test component that will inject this service: service = inject(TestService)

ng test will fail with the following error for all specs:

FAIL   project (chromium)  path/to/some.spec.ts [ path/to/some.spec.ts ]
Error: Failed to import test file /project/root/init-testbed.js
Caused by: Error: The injectable '_PlatformLocation' needs to be compiled using the JIT compiler, but '@angular/compiler' is not available.

The injectable is part of a library that has been partially compiled.
However, the Angular Linker has not processed the library such that JIT compilation is used as fallback.

Ideally, the library is processed using the Angular Linker to become fully AOT compiled.
Alternatively, the JIT compiler should be loaded by bootstrapping using '@angular/platform-browser-dynamic' or '@angular/platform-server',
or manually provide the compiler with 'import "@angular/compiler";' before bootstrapping.
 ❯ <static_initializer> node_modules/.vite/vitest/dc540563f7f56f2cac74b38788615874d1da1c10/deps/chunk-42LDSDVL.js?v=049c4943:83:17

If you remove injection of the TestService from the Test component all the specs will start to pass.

Minimal Reproduction

https://github.com/th0r/ng-vitest-test-providers-bug

Your Environment
Angular CLI       : 21.0.1
Angular           : 21.0.2
Node.js           : 24.8.0
Package Manager   : npm 11.6.0
Operating System  : darwin arm64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @angular/build            │ 21.0.1            │ ^21.0.1           │
│ @angular/cli              │ 21.0.1            │ ^21.0.1           │
│ @angular/common           │ 21.0.2            │ ^21.0.0           │
│ @angular/compiler         │ 21.0.2            │ ^21.0.0           │
│ @angular/compiler-cli     │ 21.0.2            │ ^21.0.0           │
│ @angular/core             │ 21.0.2            │ ^21.0.0           │
│ @angular/forms            │ 21.0.2            │ ^21.0.0           │
│ @angular/platform-browser │ 21.0.2            │ ^21.0.0           │
│ @angular/router           │ 21.0.2            │ ^21.0.0           │
│ rxjs                      │ 7.8.2             │ ~7.8.0            │
│ typescript                │ 5.9.3             │ ~5.9.2            │
│ vitest                    │ 4.0.14            │ ^4.0.8            │
└───────────────────────────┴───────────────────┴───────────────────┘
Lingua principale
TypeScript
Stelle
27k
Fork
11.8k
Merge medio
16h 21m
PR unite (30g)
170

Guida per i contributori

Apri la guida per i contributori

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 angular/angular-cli

Tutte le issue di angular/angular-cli

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.