Conversation
76b1451 to
1cd9122
Compare
- Update all packages and examples to Angular 20 - Update Node.js requirement to ≥20.19.0 - Update GitHub Actions workflows to use Node.js 20.19.0 - Update all Angular dependencies to version 20 - Update supporting dependencies (RxJS, TypeScript, etc.) - Update Bazel MODULE files for Angular 20 compatibility BREAKING CHANGES: - Requires Angular 20 (was Angular 19) - Requires Node.js ≥20.19.0 (was ≥18.19.1)
- Remove all tslint.json files and TSLint dependencies - Add modern ESLint 9 flat config (eslint.config.js) to all examples - Update angular.json to use @angular-eslint/builder - Clean up migration guide format and remove duplicate content - Remove obsolete tsconfig.base.json files from examples All 7 examples now build and lint cleanly with Angular 20 and modern ESLint.
Enable plugins to access builder options and target information through factory functions. This is a non-breaking enhancement - existing plugins continue to work unchanged. Plugins can now be defined as factory functions that receive builderOptions and target parameters, enabling more sophisticated plugins that can adapt their behavior based on the current build target and configuration. Co-authored-by: Matt Lewis <matt@mattlewis.me>
86c0041 to
227d553
Compare
- Update custom-esbuild to use @angular/build instead of @angular-devkit/build-angular for better performance - Update import paths to use @angular/build/private for internal APIs - Update dev-server builder context patching to use @angular/build:application - Update schema references to use @angular/build builders - Update README documentation for Angular 20 and @angular/build - Add TypeScript import fixes for better ESM support - Improve Jest examples with better Cypress config and TypeScript usage - Update common module loading logic for better CommonJS/ESM compatibility - Fix e2e tsconfig references to use correct parent tsconfig files This migration provides better performance and aligns with Angular's new build system architecture.
bc5374d to
9f1ea19
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
The repository supports Angular 19.
What is the new behavior?
Upgrades all packages, examples, and documentation to Angular 20. Updates Node.js requirement to ≥20.19.0 to match Angular 20 requirements.
Does this PR introduce a breaking change?
Breaking Changes:
Migration: Users must upgrade to Angular 20 and Node.js ≥20.19.0. Follow standard Angular 20 migration guide.
Other information
Standard major version upgrade maintaining angular-builders API compatibility + a few potentially breaking changes for major version.
Closes #1921 #1922 #1710 #1690 #1878