最近在团队中落地Vue 3 Suspense 异步组件加载， and accumulated quite a bit of experience. Here's a summary for reference, hoping it helps those doing similar work.

Core Concepts

The key lies in understanding the core logic:

import { ref, computed, watch, onMounted } from 'vue'

export default {
  setup() {
    const count = ref(0)
    const doubled = computed(() => count.value * 2)

    watch(count, (newVal, oldVal) => {
      console.log(`count: ${oldVal} -> ${newVal}`)
    })

    onMounted(() => { console.log('组件已挂载') })

    return { count, doubled }
  }
}

Performance optimization should be tailored to specific scenarios; not all cases require over-optimization.

In-Depth Analysis

We can improve it in the following ways:

import { reactive, toRefs, computed } from 'vue'

function useCounter(initial = 0) {
  const state = reactive({ count: initial, history: [initial] })
  const doubled = computed(() => state.count * 2)

  function increment() {
    state.count++
    state.history.push(state.count)
  }

  return { ...toRefs(state), doubled, increment }
}

This approach has been running stably in production for over six months and has been practically validated.

Implementation Experience

Let's start with the basic implementation:

import { ref, computed, watch, onMounted } from 'vue'

export default {
  setup() {
    const count = ref(0)
    const doubled = computed(() => count.value * 2)

    watch(count, (newVal, oldVal) => {
      console.log(`count: ${oldVal} -> ${newVal}`)
    })

    onMounted(() => { console.log('组件已挂载') })

    return { count, doubled }
  }
}

This code demonstrates the basic usage. In real projects, you also need to consider error handling and edge cases.

Optimization Strategies

Building on this foundation, we can further optimize:

import { reactive, toRefs, computed } from 'vue'

function useCounter(initial = 0) {
  const state = reactive({ count: initial, history: [initial] })
  const doubled = computed(() => state.count * 2)

  function increment() {
    state.count++
    state.history.push(state.count)
  }

  return { ...toRefs(state), doubled, increment }
}

This pattern is very practical in large projects and can significantly reduce maintenance costs.

Summary

• Understanding underlying principles is more important than memorizing APIs
• Always verify compatibility before using in production
• In team collaboration, conventions and documentation are more important than the technology itself
• Stay updated with the community; technical solutions need continuous iteration