From 38bf16a57e3e255cfd2a37ac71dc43f7d9e3b2a0 Mon Sep 17 00:00:00 2001 From: Liam DeBeasi Date: Wed, 1 Nov 2023 19:31:07 -0400 Subject: [PATCH] docs(angular): add note on migration utility (#3223) --- docs/angular/build-options.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/angular/build-options.md b/docs/angular/build-options.md index 763da398802..2f708c5e644 100644 --- a/docs/angular/build-options.md +++ b/docs/angular/build-options.md @@ -352,10 +352,18 @@ export class AppModule {} ## Migrating from Modules to Standalone +:::tip +Try our automated utility for migrating to standalone! + +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. +::: + 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. 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. +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. + ### Standalone-based Applications 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.