feat(angular): support Angular 21, drop Angular 16 and 17#31185
Open
ShaneK wants to merge 13 commits into
Open
feat(angular): support Angular 21, drop Angular 16 and 17#31185ShaneK wants to merge 13 commits into
ShaneK wants to merge 13 commits into
Conversation
…ist comment for ng18-21
…o feat/angular-21-support
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Jun 2, 2026
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.
Issue number: resolves #30907
What is the current behavior?
Ionic Angular only currently supports Angular 16-20
What is the new behavior?
Ionic Angular now supports Angular 18 through 21 and drops 16 and 17. The ng16/ng17 test apps are removed, an ng21 app is added, and the tsconfigs are tightened for the 18+ minimum.
autocorrectonion-inputandion-searchbarbecomes aboolean(defaultfalse), mapped internally to the native'on'/'off'attribute. This is required by TypeScript 5.9, which is required by Angular 21. It is the primary breaking change that forced this into a major version release of Ionic Framework.Also bundles v9 housekeeping:
@stencil/corebumped to 4.43.5 and TypeScript 5.9 in the React and Vue test apps.Does this introduce a breaking change?
The following changes are required for migration:
provideZoneChangeDetection()tobootstrapModule'sapplicationProvidersinmain.ts.ng-addonly patches standaloneapp.config.ts, notmain.ts, so the NgModule path is manual (documented in the schematic's JSDoc).autocorrectnow takestrue/falseinstead of'on'/'off'. Replaceautocorrect="on"with[autocorrect]="true"andautocorrect="off"(or the default) withfalse.Other information
Preview:
Current dev build (2025-06-02):
Docs PR: ionic-team/ionic-docs#4529