-
Notifications
You must be signed in to change notification settings - Fork 11.9k
Comparing changes
Open a pull request
base repository: angular/angular-cli
base: ccd6d8d
head repository: angular/angular-cli
compare: b2f7a03
- 5 commits
- 8 files changed
- 1 contributor
Commits on May 4, 2026
-
fix(@angular/build): use dynamic TestComponentRenderer for Vitest
This commit implements a custom TestComponentRenderer in the virtual init-testbed.js file generated for Vitest. In Vitests non-isolated mode (isolate: false) with JSDOM, Vitest creates a fresh document for each spec file but reuses the module cache. The default Angular DOMTestComponentRenderer caches the document during initialization, leading to stale references and errors like setAttribute is not a function in subsequent tests. The new DynamicDOMTestComponentRenderer looks up the document dynamically on every operation, resolving the issue without requiring a breaking change to defaults or affecting browser-based testing.
Configuration menu - View commit details
-
Copy full SHA for edfa782 - Browse repository at this point
Copy the full SHA edfa782View commit details -
fix(@schematics/angular): defer karma config deletion in Karma to Vit…
…est migration This commit resolves a race condition in the Karma-to-Vitest migration where shared configuration files were deleted prematurely within the schematic transaction. Previously, the routine erased the target file upon discovering it was identical to boilerplate, which blinded other referring projects to extraction metadata. The solution introduces analysis object caching so AST parsing occurs exactly once per discrete path. Deletion operations are deferred and batch-executed at the end of workspace processing. This mechanism guarantees continuous readability across iterating dependencies and yields operational speed improvements via memoized checks.
Configuration menu - View commit details
-
Copy full SHA for aed407d - Browse repository at this point
Copy the full SHA aed407dView commit details -
refactor(@schematics/angular): support parsing plain template literal…
…s in karma config analyzer Updates the AST analyzer to accept static backtick strings that do not contain runtime expressions. Previously, even simple template literals resulted in a fallback warning flag, triggering manual migration overrides unnecessarily.
Configuration menu - View commit details
-
Copy full SHA for 0d1f298 - Browse repository at this point
Copy the full SHA 0d1f298View commit details -
feat(@schematics/angular): update TSConfig globals during karma to vi…
…test migration Automates the transition of developer test configurations from Jasmine typing providers to Vitest globals definitions. The tool parses each collected tsconfig path and actively relocates 'vitest/globals' into the compiler options type list while removing the 'jasmine' package.
Configuration menu - View commit details
-
Copy full SHA for 8d0805d - Browse repository at this point
Copy the full SHA 8d0805dView commit details -
feat(@schematics/angular): conditionally install istanbul coverage pr…
…ovider for Vitest migration Recognize non-Chromium browser usage during the Karma to Vitest migration. While Node-based and Chromium environments can leverage @vitest/coverage-v8, browser-based test runs using engines such as Firefox or WebKit natively necessitate istanbul instrumentation.
Configuration menu - View commit details
-
Copy full SHA for b2f7a03 - Browse repository at this point
Copy the full SHA b2f7a03View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff ccd6d8d...b2f7a03