fead: added a guide

vuejs · yyx990803 · Jun 7, 2021 · May 4, 2021 · May 4, 2021 · May 4, 2021
commit d3f7da291c71dd02a4472a889f1d87081bba2c75
diff --git a/src/guide/migration/array-refs.md b/src/guide/migration/array-refs.md
@@ -73,7 +73,7 @@ Note that:
 
 ## Migration Strategy
 
-[Migration build flags:](migration-build.html)
+[Migration build flags:](migration-build.html#co
10000
mpat-configuration)
 
 - `V_FOR_REF`
 - `COMPILER_V_FOR_REF`
diff --git a/src/guide/migration/async-components.md b/src/guide/migration/async-components.md
@@ -95,4 +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)
+- [Migration build flag: `COMPONENT_ASYNC`](migration-build.html#compat-configuration)
diff --git a/src/guide/migration/attribute-coercion.md b/src/guide/migration/attribute-coercion.md
@@ -138,7 +138,7 @@ In 3.x, `null` or `undefined` should be used to explicitly remove an attribute.
   </tbody>
 </table>
 
-[Migration build flags:](migration-build.html)
+[Migration build flags:](migration-build.html#compat-configuration)
 
 - `ATTR_FALSE_VALUE`
 - `ATTR_ENUMERATED_COERSION`
diff --git a/src/guide/migration/attrs-includes-class-style.md b/src/guide/migration/attrs-includes-class-style.md
@@ -60,7 +60,7 @@ when used like this:
    <
10000
span class='blob-code-inner blob-code-marker ' data-code-marker=" ">
 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)
+[Migration build flag: `INSTANCE_ATTRS_CLASS_STYLE`](migration-build.html#compat-configuration)
 
 ## See also
 

diff --git a/src/guide/migration/children.md b/src/guide/migration/children.md
@@ -41,4 +41,4 @@ In 3.x, the `$children` property is removed and no longer supported. Instead, if
 
 ## Migration Strategy
 
-[Migration build flag: `INSTANCE_CHILDREN`](migration-build.html)
+[Migration build flag: `INSTANCE_CHILDREN`](migration-build.html#compat-configuration)
diff --git a/src/guide/migration/custom-directives.md b/src/guide/migration/custom-directives.md
@@ -105,4 +105,4 @@ With [fragments](/guide/migration/fragments.html#overview) support, components c
 
 ## Migration Strategy
 
-[Migration build flag: `CUSTOM_DIR`](migration-build.html)
+[Migration build flag: `CUSTOM_DIR`](migration-build.html#compat-configuration)
diff --git a/src/guide/migration/custom-elements-interop.md b/src/guide/migration/custom-elements-interop.md
@@ -96,7 +96,7 @@ 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)
+[Migration build flag: `COMPILER_IS_ON_ELEMENT`](migration-build.html#compat-configuration)
 
 ## `v-is` for In-DOM Template Parsing Workarounds
 

diff --git a/src/guide/migration/data-option.md b/src/guide/migration/data-option.md
@@ -111,7 +111,7 @@ In 3.0, the result will be:
 }
 ```
 
-[Migration build flag: `OPTIONS_DATA_FN`](migration-build.html)
+[Migration build flag: `OPTIONS_DATA_FN`](migration-build.html#compat-configuration)
 
 ## Migration Strategy
 
@@ -122,7 +122,7 @@ For users relying on the object declaration, we recommend:
 
 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)
+[Migration build flags:](migration-build.html#compat-configuration)
 
 - `OPTIONS_DATA_FN`
 - `OPTIONS_DATA_MERGE`
diff --git a/src/guide/migration/events-api.md b/src/guide/migration/events-api.md
@@ -80,4 +80,4 @@ 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)
+[Migration build flag: `INSTANCE_EVENT_EMITTER`](migration-build.html#compat-configuration)
diff --git a/src/guide/migration/filters.md b/src/guide/migration/filters.md
@@ -73,7 +73,7 @@ Using the example above, here is one example of how it could be implemented.
 
 Instead of using filters, we recommend replacing them with computed properties or methods.
 
-[Migration build flags:](migration-build.html)
+[Migration build flags:](migration-build.html#compat-configuration)
 
 - `FILTERS`
 - `COMPILER_FILTERS`

diff --git a/src/guide/migration/functional-components.md b/src/guide/migration/functional-components.md
@@ -110,4 +110,4 @@ For more information on the usage of the new functional components and the chang
 
 - [Migration: Render Functions](/guide/migration/render-function-api.html)
 - [Guide: Render Functions](/guide/render-function.html)
-- [Migration build flag: `COMPONENT_FUNCTIONAL`](migration-build.html)
+- [Migration build flag: `COMPONENT_FUNCTIONAL`](migration-build.html#compat-configuration)
diff --git a/src/guide/migration/global-api.md b/src/guide/migration/global-api.md
@@ -95,7 +95,7 @@ In Vue 3.x, the "use production build" tip will only show up when using the "dev
 
 For ES modules builds, since they are used with bundlers, and in most cases a CLI or boilerplate would have configured the production env properly, this tip will no longer show up.
 
-[Migration build flag: `CONFIG_PRODUCTION_TIP`](migration-build.html)
+[Migration build flag: `CONFIG_PRODUCTION_TIP`](migration-build.html#compat-configuration)
 
 ### `config.ignoredElements` Is Now `config.isCustomElement`
@@ -118,7 +118,7 @@ In Vue 3, the check of whether an element is a component or not has been moved t
 - This will be a new top-level option in the Vue CLI config.
   :::
 
-[Migration build flag: `CONFIG_IGNORED_ELEMENTS`](migration-build.html)
+[Migration build flag: `CONFIG_IGNORED_ELEMENTS`](migration-build.html#compat-configuration)
 
 ### `Vue.prototype` Replaced by `config.globalProperties`
 
@@ -139,7 +139,7 @@ app.config.globalProperties.$http = () => {}
 
 Using `provide` (discussed [below](#provide-inject)) should also be considered as an alternative to `globalProperties`.
 
-[Migration build flag: `GLOBAL_PROTOTYPE`](migration-build.html)
+[Migration build flag: `GLOBAL_PROTOTYPE`](migration-build.html#compat-configuration)
 
 ### `Vue.extend` Replaced by `defineComponent`
 
@@ -179,7 +179,7 @@ const Profile = defineComponent({
 })
 ```
 
-[Migration build flag: `GLOBAL_EXTEND`](migration-build.html)
+[Migration build flag: `GLOBAL_EXTEND`](migration-build.html#compat-configuration)
 
 ### A Note for Plugin Authors
 
@@ -234,7 +234,7 @@ app.directive('focus', {
 app.mount('#app')
 ```
 
-[Migration build flag: `GLOBAL_MOUNT`](migration-build.html)
+[Migration build flag: `GLOBAL_MOUNT`](migration-build.html#compat-configuration)
 
 ## Provide / Inject
 

diff --git a/src/guide/migration/inline-template-attribute.md b/src/guide/migration/inline-template-attribute.md
@@ -30,7 +30,7 @@ This feature will no longer be supported.
 
 Most of the use cases for `inline-template` assumes a no-build-tool setup, where all templates are written directly inside the HTML page.
 
-[Migration build flag: `COMPILER_INLINE_TEMPLATE`](migration-build.html)
+[Migration build flag: `COMPILER_INLINE_TEMPLATE`](migration-build.html#compat-configuration)
 
 ### Option #1: Use `<script>` tag
 

diff --git a/src/guide/migration/keycode-modifiers.md b/src/guide/migration/keycode-modifiers.md
@@ -55,7 +55,7 @@ As a result, this means that `config.keyCodes` is now also deprecated and will n
 
 For those using `keyCode` in their codebase, we recommend converting them to their kebab-cased named equivalents.
 
-[Migration build flags:](migration-build.html)
+[Migration build flags:](migration-build.html#compat-configuration)
 
 - `CONFIG_KEY_CODES`
 - `V_ON_KEYCODE_MODIFIER`
diff --git a/src/guide/migration/listeners-removed.md b/src/guide/migration/listeners-removed.md
@@ -65,7 +65,7 @@ If this component received an `id` attribute and a `v-on:close` listener, the `$
 
 Remove all usages of `$listeners`.
 
-[Migration build flag: `INSTANCE_LISTENERS`](migration-build.html)
+[Migration build flag: `INSTANCE_LISTENERS`](migration-build.html#compat-configuration)
 
 ## See also
Original file line number	Diff line number	Diff line change
Expand Up		@@ -41,4 +41,4 @@ In 3.x, the `$children` property is removed and no longer supported. Instead, if

		## Migration Strategy

		[Migration build flag: `INSTANCE_CHILDREN`](migration-build.html)
		[Migration build flag: `INSTANCE_CHILDREN`](migration-build.html#compat-configuration)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -105,4 +105,4 @@ With [fragments](/guide/migration/fragments.html#overview) support, components c

		## Migration Strategy

		[Migration build flag: `CUSTOM_DIR`](migration-build.html)
		[Migration build flag: `CUSTOM_DIR`](migration-build.html#compat-configuration)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -80,4 +80,4 @@ 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)
		[Migration build flag: `INSTANCE_EVENT_EMITTER`](migration-build.html#compat-configuration)