Skip to content

Commit 38bf16a

Browse files
authored
docs(angular): add note on migration utility (#3223)
1 parent 54317c1 commit 38bf16a

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

docs/angular/build-options.md

+8
Original file line numberDiff line numberDiff line change
@@ -352,10 +352,18 @@ export class AppModule {}
352352

353353
## Migrating from Modules to Standalone
354354

355+
:::tip
356+
Try our automated utility for migrating to standalone!
357+
358+
See https://github.com/ionic-team/ionic-angular-standalone-codemods for instructions on how to get started. All issues related to the migration utility should be filed on the linked repo.
359+
:::
360+
355361
The Standalone option is newer than the Modules option, so developers may wish to switch during the development of their application. This guide details the steps needed to migrate.
356362

357363
Migrating to Ionic standalone components must be done all at the same time and cannot be done gradually. The Modules and Standalone approaches use two different build systems of Ionic that cannot be used at the same time.
358364

365+
Developers are encouraged to try the [automated migration utility](https://github.com/ionic-team/ionic-angular-standalone-codemods), though they can also follow the steps below if they would like to manually migrate their applications.
366+
359367
### Standalone-based Applications
360368

361369
Follow these steps if your Angular application is already using the standalone architecture, and you want to use Ionic UI components as standalone components too.

0 commit comments

Comments
 (0)