|
| 1 | +# Dynamic & Async Components |
| 2 | + |
| 3 | +> This page assumes you've already read the [Components Basics](components.md). Read that first if you are new to components. |
| 4 | +
|
| 5 | +## `keep-alive` with Dynamic Components |
| 6 | + |
| 7 | +Earlier, we used the `is` attribute to switch between components in a tabbed interface: |
| 8 | + |
| 9 | +```html |
| 10 | +<component v-bind:is="currentTabComponent"></component> |
| 11 | +``` |
| 12 | + |
| 13 | +When switching between these components though, you'll sometimes want to maintain their state or avoid re-rendering for performance reasons. For example, when expanding our tabbed interface a little: |
| 14 | + |
| 15 | +<dynamic-1/> |
| 16 | + |
| 17 | +You'll notice that if you select a post, switch to the _Archive_ tab, then switch back to _Posts_, it's no longer showing the post you selected. That's because each time you switch to a new tab, Vue creates a new instance of the `currentTabComponent`. |
| 18 | + |
| 19 | +Recreating dynamic components is normally useful behavior, but in this case, we'd really like those tab component instances to be cached once they're created for the first time. To solve this problem, we can wrap our dynamic component with a `<keep-alive>` element: |
| 20 | + |
| 21 | +```html |
| 22 | +<!-- Inactive components will be cached! --> |
| 23 | +<keep-alive> |
| 24 | + <component v-bind:is="currentTabComponent"></component> |
| 25 | +</keep-alive> |
| 26 | +``` |
| 27 | + |
| 28 | +Check out the result below: |
| 29 | + |
| 30 | +<dynamic-2/> |
| 31 | + |
| 32 | +Now the _Posts_ tab maintains its state (the selected post) even when it's not rendered. See [this example](https://codesandbox.io/s/github/vuejs/vuejs.org/tree/master/src/v2/examples/vue-20-keep-alive-with-dynamic-components) for the complete code. |
| 33 | + |
| 34 | +:::tip Note |
| 35 | +Note that `<keep-alive>` requires the components being switched between to all have names, either using the `name` option on a component, or through local/global registration |
| 36 | +::: |
| 37 | + |
| 38 | +Check out more details on `<keep-alive>` in the [API reference](TODO:../api/#keep-alive). |
| 39 | + |
| 40 | +## Async Components |
| 41 | + |
| 42 | +In large applications, we may need to divide the app into smaller chunks and only load a component from the server when it's needed. To make that easier, Vue allows you to define your component as a factory function that asynchronously resolves your component definition. Vue will only trigger the factory function when the component needs to be rendered and will cache the result for future re-renders. For example: |
| 43 | + |
| 44 | +```js |
| 45 | +Vue.component('async-example', function(resolve, reject) { |
| 46 | + setTimeout(function() { |
| 47 | + // Pass the component definition to the resolve callback |
| 48 | + resolve({ |
| 49 | + template: '<div>I am async!</div>' |
| 50 | + }) |
| 51 | + }, 1000) |
| 52 | +}) |
| 53 | +``` |
| 54 | + |
| 55 | +As you can see, the factory function receives a `resolve` callback, which should be called when you have retrieved your component definition from the server. You can also call `reject(reason)` to indicate the load has failed. The `setTimeout` here is for demonstration; how to retrieve the component is up to you. One recommended approach is to use async components together with [Webpack's code-splitting feature](https://webpack.js.org/guides/code-splitting/): |
| 56 | + |
| 57 | +```js |
| 58 | +Vue.component('async-webpack-example', function(resolve) { |
| 59 | + // This special require syntax will instruct Webpack to |
| 60 | + // automatically split your built code into bundles which |
| 61 | + // are loaded over Ajax requests. |
| 62 | + require(['./my-async-component'], resolve) |
| 63 | +}) |
| 64 | +``` |
| 65 | + |
| 66 | +You can also return a `Promise` in the factory function, so with Webpack 2 and ES2015 syntax you can do: |
| 67 | + |
| 68 | +```js |
| 69 | +Vue.component( |
| 70 | + 'async-webpack-example', |
| 71 | + // The `import` function returns a Promise. |
| 72 | + () => import('./my-async-component') |
| 73 | +) |
| 74 | +``` |
| 75 | + |
| 76 | +When using [local registration](components-registration.html#Local-Registration), you can also directly provide a function that returns a `Promise`: |
| 77 | + |
| 78 | +```js |
| 79 | +new Vue({ |
| 80 | + // ... |
| 81 | + components: { |
| 82 | + 'my-component': () => import('./my-async-component') |
| 83 | + } |
| 84 | +}) |
| 85 | +``` |
| 86 | + |
| 87 | +<p class="tip">If you're a <strong>Browserify</strong> user that would like to use async components, its creator has unfortunately [made it clear](https://github.com/substack/node-browserify/issues/58#issuecomment-21978224) that async loading "is not something that Browserify will ever support." Officially, at least. The Browserify community has found [some workarounds](https://github.com/vuejs/vuejs.org/issues/620), which may be helpful for existing and complex applications. For all other scenarios, we recommend using Webpack for built-in, first-class async support.</p> |
| 88 | + |
| 89 | +### Handling Loading State |
| 90 | + |
| 91 | +> New in 2.3.0+ |
| 92 | +
|
| 93 | +The async component factory can also return an object of the following format: |
| 94 | + |
| 95 | +```js |
| 96 | +const AsyncComponent = () => ({ |
| 97 | + // The component to load (should be a Promise) |
| 98 | + component: import('./MyComponent.vue'), |
| 99 | + // A component to use while the async component is loading |
| 100 | + loading: LoadingComponent, |
| 101 | + // A component to use if the load fails |
| 102 | + error: ErrorComponent, |
| 103 | + // Delay before showing the loading component. Default: 200ms. |
| 104 | + delay: 200, |
| 105 | + // The error component will be displayed if a timeout is |
| 106 | + // provided and exceeded. Default: Infinity. |
| 107 | + timeout: 3000 |
| 108 | +}) |
| 109 | +``` |
| 110 | + |
| 111 | +> Note that you must use [Vue Router](https://github.com/vuejs/vue-router) 2.4.0+ if you wish to use the above syntax for route components. |
0 commit comments