Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(angular): add links to Angular's standalone migration guide #3150

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/angular/build-options.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,10 @@ See the [Standalone Migration Guide](#migrating-from-modules-to-standalone) for
All Ionic imports should be imported from the `@ionic/angular/standalone` submodule. This includes imports such as components, directives, providers, and types. Importing from `@ionic/angular` may pull in lazy loaded Ionic code which can interfere with treeshaking.
:::

:::info
This section assumes your application has already been converted to use Angular's standalone architecture. For information on migrating, see [Angular's migration guide](https://angular.io/guide/standalone-migration).
:::

**Bootstrapping and Configuration**

Ionic Angular needs to be configured when the Angular application calls `bootstrapApplication` using the `provideIonicAngular` function. Developers can pass any [IonicConfig](../developing/config#ionicconfig) values as an object in this function. Note that `provideIonicAngular` needs to be called even if no custom config is passed.
Expand Down Expand Up @@ -154,6 +158,10 @@ The Standalone option is newer than the Modules option, so developers may wish t

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.

:::info
Migrating your Angular application to use the standalone architecture is optional when using Ionic's standalone components, but the two processes are separate. For information on migrating your application as a whole, see [Angular's migration guide](https://angular.io/guide/standalone-migration).
:::

### 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.
Expand Down
Loading