prefer-ionic-standalone

Prefer the Ionic 9 standalone API and disallow IonicModule and obsolete or NgModule-based entry points.

• ⭐️ This rule is included in plugin:@rdlabo/rules/recommended preset.
• ✒️ The --fix option on the command line can automatically fix some of the problems reported by this rule.

Ionic 9 exports standalone Angular components from @ionic/angular. This rule keeps applications on that API surface by rejecting the obsolete @ionic/angular/standalone entry point, the NgModule-based @ionic/angular/lazy entry point, and IonicModule itself.

Rule Details

The rule checks imports, named re-exports, export-all declarations, and IonicModule access through a namespace import. Namespace access is resolved by scope, so a shadowed local variable with the same name is not reported.

Examples

Incorrect

import { IonButton } from '@ionic/angular/standalone';
import { IonInput } from '@ionic/angular/lazy';
import { IonicModule } from '@ionic/angular';

Correct

import { IonButton, IonInput, ModalController, provideIonicAngular } from '@ionic/angular';

Named imports and named re-exports from /standalone and /lazy are auto-fixed to @ionic/angular, preserving the original quote style. Side-effect imports, namespace imports, and export * declarations are reported without a fix because changing their entry point may change runtime behavior. IonicModule is also reported without a fix because replacing IonicModule.forRoot() and NgModule metadata requires application-level changes.

Options

This rule has no options. Configure its severity as warn or error in ESLint configuration.

When to enable

Enable this rule in Ionic 9 Angular applications after adopting standalone bootstrap. NgModule applications should complete the standalone migration before enabling it because @ionic/angular/lazy and IonicModule are always rejected.

Implementation

• Rule source
• Test source