feat(angular): make standalone imports default

[OS-jacobbell]

What is the current behavior?

The default path for imports is @ionic/angular and imports the lazy-loaded angular components. @ionic/angular/standalone imports the standalone components.

What is the new behavior?

The default path, @ionic/angular, imports standalone components. Lazy-loaded components are imported from @ionic/angular/lazy.

Does this introduce a breaking change?

• Yes
• No

Applications that use lazy-loaded angular components will need to update their import paths from @ionic/angular to @ionic/angular/lazy.
Applications that use standalone angular components will need to update their import paths from @ionic/angular/standalone to @ionic/angular.

Other information

Ionic starters will need their import paths updated to match these changes.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
ionic-framework	Ready	Preview, Comment	Jul 1, 2026 3:00pm

[ShaneK]

Awesome work! Just a few problems below, but I also noticed a couple of other problems outside the diff scope:

• BREAKING.md wasn't updated, and it definitely should be for this. This is a massive breaking change. Worth a migration note: @ionic/angular/standalone becomes @ionic/angular, and @ionic/angular becomes @ionic/angular/lazy. The existing Module Resolution section also uses @ionic/angular/standalone as its example subpath (BREAKING.md:203), which no longer exists after this change.
• The Project Structure section in packages/angular/README.md (lines 96-114) is now stale. It still describes a src submodule imported from @ionic/angular and standalone imported from @ionic/angular/standalone, both reversed and renamed now.

[ShaneK]

Awesome! Thanks! Two minor doc change requests, but not blocking

[thetaPC]

LGTM

[brandyscarney]

Looks good to me!