-
Notifications
You must be signed in to change notification settings - Fork 12k
Comparing changes
Open a pull request
base repository: angular/angular-cli
base: 20.0.0
head repository: angular/angular-cli
compare: 20.0.1
- 7 commits
- 15 files changed
- 3 contributors
Commits on May 29, 2025
-
fix(@angular/build): also disable outputMode in vitest unit-tests
Application defined entry points (`browser`/`server`) are disabled when using the experimental unit-test builder. This allows the unit test files themselves to become the entry points for testing purposes. Previously, the `outputMode` option was not also disabled. This lead to errors if it was present in the build target configuration used for `unit-test` due to the `outputMode` option requiring the `server` option. (cherry picked from commit 020527e)
Configuration menu - View commit details
-
Copy full SHA for e5efdc5 - Browse repository at this point
Copy the full SHA e5efdc5View commit details -
fix(@schematics/angular): only overwrite JSON file if actually changed
The JSON file helper utility used within the Angular schematics now contains additional checks when attempting to modify a file to avoid overwriting a file if no actual changes will occur after a modify request. (cherry picked from commit 664e6c7)
Configuration menu - View commit details
-
Copy full SHA for 525ddcb - Browse repository at this point
Copy the full SHA 525ddcbView commit details -
fix(@schematics/angular): remove karma config devkit package usages d…
…uring application migration When performing an `ng update` to Angular v20, the application migration will detect the usage of the `karma` builder's `karmaConfig` option and attempt to remove usages of the no longer needed `@angular-devkit/build-angular` karma framework and plugin usage. While the karma framework usage will be specifically ignored when using the `@angular/build:karma` builder, the plugin usage leverages a direct `require` within the configuration file. Regardless of the ability of the builder to ignore, neither usage is needed with `@angular/build:karma` and removing the code aligns with what would be generated by `ng generate config karma`. (cherry picked from commit a2aba4c)
Configuration menu - View commit details
-
Copy full SHA for 83c820e - Browse repository at this point
Copy the full SHA 83c820eView commit details
Commits on Jun 3, 2025
-
fix(@angular/build): resolve junit karma reporter output to workspace…
… root To maintain behavior with the Webpack-based karma unit-testing available via `@angular-devkit/build-angular`, the application build system based karma testing will now resolve the output directory location of the junit karma reporter to the same workspace root location. This is only performed if the `junit` reporter is enabled and the reporter's `outputDir` option is not an absolute path. (cherry picked from commit bec42f7)
Configuration menu - View commit details
-
Copy full SHA for 5814393 - Browse repository at this point
Copy the full SHA 5814393View commit details -
fix(@schematics/angular): skip zone.js dependency for zoneless applic…
…ations A newly generated application no longer adds the `zone.js` dependency to the workspace if the `zoneless` option is enabled. (cherry picked from commit 7ca250a)
Configuration menu - View commit details
-
Copy full SHA for 87266b3 - Browse repository at this point
Copy the full SHA 87266b3View commit details
Commits on Jun 4, 2025
-
fix(@angular/cli): improve Node.js version check and error messages
Enhances the Node.js version validation to include Node.js 22.12 (cherry picked from commit abe69dd)
Configuration menu - View commit details
-
Copy full SHA for 0883248 - Browse repository at this point
Copy the full SHA 0883248View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4e7e0b0 - Browse repository at this point
Copy the full SHA 4e7e0b0View 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 20.0.0...20.0.1