more updates per feedback

Author: yyx990803

src/api/directives.md

@@ -464,8 +464,11 @@
   </ul>
   ```
 
+  Since 3.2, you can also memoize part of the template with invalidation conditions using [`v-memo`](#v-memo).
+
 - **See also:**
   - [Data Binding Syntax - interpolations](../guide/template-syntax.html#text)
+  - [v-memo](#v-memo)
 
 ## v-memo <Badge text="3.2+" />
 
@@ -483,7 +486,7 @@
 
   When the component re-renders, if both `valueA` and `valueB` remain the same, all updates for this `<div>` and its children will be skipped. In fact, even the Virtual DOM VNode creation will also be skipped since the memoized copy of the sub-tree can be reused.
 
-  It is important to specify the memoization array correctly, otherwise we may skip updates that should indeed be applied.
+  It is important to specify the memoization array correctly, otherwise we may skip updates that should indeed be applied. `v-memo` with an empty dependency array (`v-memo="[]"`) would be functionally equivalent to `v-once`.
 
   This directive is provided solely for micro optimizations in performance-critical scenarios and should be rarely needed. The most common case where this may prove helpful is when rendering large `v-for` lists (where `length > 1000`):
 
@@ -498,6 +501,9 @@
 
   `v-memo` can also be used on components to manually prevent unwanted updates in certain edge cases where the child component update check has been de-optimized. But again, it is the developer's responsibility to specify correct dependency arrays to avoid skipping necessary updates.
 
+- **See also:**
+  - [v-once](#v-once)
+
 ## v-is <Badge text="deprecated" type="warning" />
 
 Deprecated in 3.1.0. Use [`is` attribute with `vue:` prefix](/api/special-attributes.html#is) instead.

src/api/global-api.md

@@ -265,9 +265,11 @@ customElements.define('my-vue-element', MyVueElement)
 
 // You can also programmatically instantiate the element:
 // (can only be done after registration)
-document.body.appendChild(new MyVueElement({
-  // initial props (optional)
-}))
+document.body.appendChild(
+  new MyVueElement({
+    // initial props (optional)
+  })
+)
 ```
 
 For more details on building Web Components with Vue, especially with Single File Components, see [Vue and Web Components](/guide/web-components.html#building-custom-elements-with-vue).
@@ -565,7 +567,7 @@ export default {
 </style>
 ```
 
-For more information about using CSS modules, see [Vue Loader - CSS Modules](https://vue-loader.vuejs.org/guide/css-modules.html).
+For more information about using CSS modules, see [SFC Style Features: `<style module>`](/api/sfc-style.html#style-module).
 
 ### Arguments
 

src/api/sfc-script-setup.md

@@ -148,6 +148,8 @@ To explicitly expose properties in a `<script setup>` component, use the `define
 
 ```vue
 <script setup>
+import { ref } from 'vue'
+
 const a = 1
 const b = ref(2)
 
@@ -212,6 +214,10 @@ const post = await fetch(`/api/post/1`).then(r => r.json())
 
 In addition, the awaited expression will be automatically compiled in a format that preserves the current component instance context after the `await`.
 
+:::warning Note
+`async setup()` must be used in combination with `Suspense`, which is currently still an experimental feature. We plan to finalize and document it in a future release - but if you are curious now, you can refer to its [tests](https://github.com/vuejs/vue-next/blob/master/packages/runtime-core/__tests__/components/Suspense.spec.ts) to see how it works.
+:::
+
 ## TypeScript-only Features
 
 ### Type-only props/emit declarations
@@ -236,7 +242,7 @@ const emit = defineEmits<{
 
   - In dev mode, the compiler will try to infer corresponding runtime validation from the types. For example here `foo: String` is inferred from the `foo: string` type. If the type is a reference to an imported type, the inferred result will be `foo: null` (equal to `any` type) since the compiler does not have information of external files.
 
-  - In prod mode, the compiler will generate the array format declaration to reduce bundle size (the props here will be compiled into `['msg']`)
+  - In prod mode, the compiler will generate the array format declaration to reduce bundle size (the props here will be compiled into `['foo', 'bar']`)
 
   - The emitted code is still TypeScript with valid typing, which can be further processed by other tools.
 
@@ -254,10 +260,12 @@ One drawback of the type-only `defineProps` declaration is that it doesn't have
 ```ts
 interface Props {
   msg?: string
+  labels?: string[]
 }
 
 const props = withDefaults(defineProps<Props>(), {
-  msg: 'hello'
+  msg: 'hello',
+  labels: () => ['one', 'two']
 })
 ```
 

src/api/sfc-style.md

@@ -144,6 +144,18 @@ You can customize the property key of the injected classes object by giving the
 </style>
 ```
 
+### Usage with Composition API
+
+The injected classes can be accessed in `setup()` and `<script setup>` via the [`useCssModule`](/api/global-api.html#usecssmodule) API. For `<style module>` blocks with custom injection names, `useCssModule` accepts the matching `module` attribute value as the first argument:
+
+```js
+// default, returns classes for <style module>
+useCssModule()
+
+// named, returns classes for <style module="classes">
+useCssModule('classes')
+```
+
 ## State-Driven Dynamic CSS
 
 SFC `<style>` tags support linking CSS values to dynamic component state using the `v-bind` CSS function: