Skip to content

Commit

Permalink
Update global-api-treeshaking.md (#1254)
Browse files Browse the repository at this point in the history
  • Loading branch information
doksara authored Sep 23, 2021
1 parent feb467b commit a2bb521
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion src/guide/migration/global-api-treeshaking.md
Original file line number Diff line number Diff line change
Expand Up @@ -107,7 +107,7 @@ export function render() {

This essentially means the `Transition` component only gets imported when the application actually makes use of it. In other words, if the application doesn’t have any `<transition>` component, the code supporting this feature will not be present in the final bundle.

With global tree-shaking, the user only “pay” for the features they actually use. Even better, knowing that optional features won't increase the bundle size for applications not using them, framework size has become much less a concern for additional core features in the future, if at all.
With global tree-shaking, the users only “pay” for the features they actually use. Even better, knowing that optional features won't increase the bundle size for applications not using them, framework size has become much less a concern for additional core features in the future, if at all.

::: warning Important
The above only applies to the [ES Modules builds](/guide/installation.html#explanation-of-different-builds) for use with tree-shaking capable bundlers - the UMD build still includes all features and exposes everything on the Vue global variable (and the compiler will produce appropriate output to use APIs off the global instead of importing).
Expand Down

0 comments on commit a2bb521

Please sign in to comment.