Migration build (vuejs#1033)

Author: NataliaTepluhina

src/.vuepress/config.js

@@ -172,6 +172,7 @@ const sidebar = {
   ],
   migration: [
     '/guide/migration/introduction',
+    '/guide/migration/migration-build',
     {
       title: 'Details',
       collapsable: false,

src/guide/migration/array-refs.md

@@ -70,3 +70,10 @@ Note that:
 - `itemRefs` doesn't have to be an array: it can also be an object where the refs are set by their iteration keys.
 
 - This also allows `itemRefs` to be made reactive and watched, if needed.
+
+## Migration Strategy
+
+[Migration build flags:](migration-build.html#compat-configuration)
+
+- `V_FOR_REF`
+- `COMPILER_V_FOR_REF`

src/guide/migration/async-components.md

@@ -95,3 +95,4 @@ const asyncComponent = defineAsyncComponent(
 For more information on the usage of async components, see:
 
 - [Guide: Dynamic & Async Components](/guide/component-dynamic-async.html#dynamic-components-with-keep-alive)
+- [Migration build flag: `COMPONENT_ASYNC`](migration-build.html#compat-configuration)

src/guide/migration/attribute-coercion.md

@@ -137,3 +137,8 @@ In 3.x, `null` or `undefined` should be used to explicitly remove an attribute.
     </tr>
   </tbody>
 </table>
+
+[Migration build flags:](migration-build.html#compat-configuration)
+
+- `ATTR_FALSE_VALUE`
+- `ATTR_ENUMERATED_COERSION`

src/guide/migration/attrs-includes-class-style.md

@@ -60,6 +60,8 @@ when used like this:
 
 In components that use `inheritAttrs: false`, make sure that styling still works as intended. If you previously relied on the special behavior of `class` and `style`, some visuals might be broken as these attributes might now be applied to another element.
 
+[Migration build flag: `INSTANCE_ATTRS_CLASS_STYLE`](migration-build.html#compat-configuration)
+
 ## See also
 
 - [Relevant RFC](https://github.com/vuejs/rfcs/blob/master/active-rfcs/0031-attr-fallthrough.md)

src/guide/migration/children.md

@@ -38,3 +38,7 @@ export default {
 ## 3.x Update
 
 In 3.x, the `$children` property is removed and no longer supported. Instead, if you need to access a child component instance, we recommend using [$refs](/guide/component-template-refs.html#template-refs).
+
+## Migration Strategy
+
+[Migration build flag: `INSTANCE_CHILDREN`](migration-build.html#compat-configuration)

src/guide/migration/custom-directives.md

@@ -103,3 +103,7 @@ mounted(el, binding, vnode) {
 :::warning
 With [fragments](/guide/migration/fragments.html#overview) support, components can potentially have more than one root node. When applied to a multi-root component, a custom directive will be ignored and a warning will be logged.
 :::
+
+## Migration Strategy
+
+[Migration build flag: `CUSTOM_DIR`](migration-build.html#compat-configuration)

src/guide/migration/custom-elements-interop.md

@@ -96,6 +96,8 @@ In 3.0, we are limiting Vue's special treatment of the `is` prop to the `<compon
     document.createElement('button', { is: 'plastic-button' })
     ```
 
+[Migration build flag: `COMPILER_IS_ON_ELEMENT`](migration-build.html#compat-configuration)
+
 ## `v-is` for In-DOM Template Parsing Workarounds
 
 > Note: this section only affects cases where Vue templates are directly written in the page's HTML.

src/guide/migration/data-option.md

@@ -111,6 +111,8 @@ In 3.0, the result will be:
 }
 ```
 
+[Migration build flag: `OPTIONS_DATA_FN`](migration-build.html#compat-configuration)
+
 ## Migration Strategy
 
 For users relying on the object declaration, we recommend:
@@ -119,3 +121,8 @@ For users relying on the object declaration, we recommend:
 - Rewrite references to the shared data to point to a new shared object
 
 For users relying on the deep merge behavior from mixins, we recommend refactoring your code to avoid such reliance altogether, since deep merges from mixins are very implicit and can make the code logic more difficult to understand and debug.
+
+[Migration build flags:](migration-build.html#compat-configuration)
+
+- `OPTIONS_DATA_FN`
+- `OPTIONS_DATA_MERGE`

src/guide/migration/events-api.md

@@ -79,3 +79,5 @@ export default {
 This provides the same event emitter API as in Vue 2.
 
 These methods may also be supported in a future compatibility build of Vue 3.
+
+[Migration build flag: `INSTANCE_EVENT_EMITTER`](migration-build.html#compat-configuration)