This guide covers how routing works in an app built with Ionic and Vue.
IonRouterOutlet component uses the popular Vue Router library under the hood. With Ionic and Vue Router, you can create multi-page apps with rich page transitions.
Everything you know about routing using Vue Router carries over into Ionic Vue. Let's take a look at the basics of an Ionic Vue app and how routing works with it.
While reading this guide, you may notice that most of these concepts are very similar to the concepts found in Vue Router without Ionic Framework. You observation would be correct! Ionic Vue leverages the best parts of Vue Router to make the transition to building apps with Ionic Framework as seamless as possible. As a result, we recommend relying on Vue Router features as much as possible rather than trying to build your own routing solutions.
Here is a sample routing configuration that defines a single route to the "/home" URL. When you visit "/home", the route renders the
On the app's initial load, the app will render the
HomePage component as that is what is configured here.
What if we wanted to land a different path on our initial load? For this, we can use router redirects. Redirects work the same way that a typical route object does, but just includes some different keys:
In our redirect, we look for the index path of our app. Then if we load that, we redirect to the
This is all great, but how does one actually navigate to a route? For this, we can use the
router-link property. Let's create a new routing setup:
Say we start on the
home route, and we want to add a button that takes us to the
detail route. We can do this using the following HTML to navigate to the
We can also programmatically navigate in our app by using the router API:
Both options provide the same navigation mechanism, just fitting different use cases.
The current way our routes are setup makes it so they are included in the same initial chunk when loading the app, which is not always ideal. Instead, we can set up our routes so that components are loaded as they are needed:
Here, we have the same setup as before only this time
DetailPage has been replaced with an import call. This will result in the
DetailPage component no longer being part of the chunk that is requested on application load.
A common point of confusion when setting up routing is deciding between shared URLs or nested routes. This part of the guide will explain both and help you decide which one to use.
Shared URLs is a route configuration where routes have pieces of the URL in common. The following is an example of a shared URL configuration:
The above routes are considered "shared" because they reuse the
dashboard piece of the URL.
Nested Routes is a route configuration where routes are listed as children of other routes. The following is an example of a nested route configuration:
The above routes are nested because they are in the
children array of the parent route. Notice that the parent route renders the
DashboardRouterOutlet component. When you nest routes, you need to render another instance of
Shared URLs are great when you want to transition from page A to page B while preserving the relationship between the two pages in the URL. In our previous example, a button on the
/dashboard page could transition to the
/dashboard/stats page. The relationship between the two pages is preserved because of a) the page transition and b) the url.
Nested routes are mostly useful when you need to render content in outlet A while also rendering sub-content inside of a nested outlet B. The most common use case you will run into is tabs. When you load up a tabs Ionic starter application, you will see
ion-tabs components rendered in the first
ion-tabs component renders another
ion-router-outlet which is responsible for rendering the contents of each tab.
There are very few use cases in which nested routes make sense in mobile applications. When in doubt, use the shared URL route configuration. We strongly caution against using nested routing in contexts other than tabs as it can quickly make navigating your app confusing.
When working with tabs, Ionic Vue needs a way to know which view belongs to which tab. The
IonTabs component comes in handy here, but let's look at what the routing setup for this looks like:
tabs path loads a
Tabs component. We provide each tab as a route object inside of the
children array. In this example, we call the path
tabs, but this can be customized.
Let's start by taking a look at our
If you have worked with Ionic Framework before, this should feel familiar. We create an
ion-tabs component, and provide an
ion-tab-bar provides and
ion-tab-button components, each with a
tab property that is associated with its corresponding tab in the router config.
When adding additional routes to tabs you should write them as sibling routes with the parent tab as the path prefix. The example below defines the
/tabs/tab1/view route as a sibling of the
/tabs/tab1 route. Since this new route has the
tab1 prefix, it will be rendered inside of the
Tabs component, and Tab 1 will still be selected in the
IonRouterOutlet component provides a container to render your views in. It is similar to the
RouterView component found in other Vue applications except that
IonRouterOutlet can render multiple pages in the DOM in the same outlet. When a component is rendered in
IonRouterOutlet we consider this to be an Ionic Framework "page". The router outlet container controls the transition animation between the pages as well as controls when a page is created and destroyed. This helps maintain the state between the views when switching back and forth between them.
Nothing should be provided inside of
IonRouterOutlet when setting it up in your template. While
IonRouterOutlet can be nested in child components, we caution against it as it typically makes navigation in apps confusing. See Shared URLs versus Nested Routes for more information.
IonPage component wraps each view in an Ionic Vue app and allows page transitions and stack navigation to work properly. Each view that is navigated to using the router must include an
Components presented via
IonPopover do not typically need an
IonPage component unless you need a wrapper element. In that case, we recommend using
IonPage so that the component dimensions are still computed properly.
There may be a few use cases where you need to get access to the
IonRouter instance from within your Vue application. For example, you might want to know if you are at the root page of the application when a user presses the hardware back button on Android. For use cases like these, you can inject the
IonRouter dependency into your component:
Let's expand upon our original routing example to show how we can use URL parameters:
Notice that we have now added
:id to the end of our
detail path string. URL parameters are dynamic portions of our route paths. When the user navigates to a URL such as
/details/1 the "1" is saved to a parameter named "id" which can be accessed in the component when the route renders.
Let's look at how to use it in our component:
route variable contains an instance of the current route. It also contains any parameters we have passed in. We can obtain the
id parameter from here and display it on the screen.
Vue Router ships with a configurable history mode. Let's look at the different options and why you might want to use each one.
createWebHistory: This option creates an HTML5 history. It leverages the History API to achieve URL navigation without a page reload. This is the most common history mode for single page applications. When in doubt, use
createWebHashHistory: This option adds a hash (
#) to your URL. This is useful for web applications with no host or when you do not have full control over the server routes. Search engines sometimes ignore hash fragments, so you should use
createWebHistoryinstead if SEO is important for your application.
createMemoryHistory: This option creates an in-memory based history. This is mainly used to handle server-side rendering (SSR).
For more info on routing in Vue using Vue Router, check out their docs at http://router.vuejs.org/.