In day-to-day development, Nuxt 3.11 New Features Overview is being used more and more frequently. This article systematically explains its usage, principles, and optimization strategies.

Quick Start

Usage in real projects tends to be more complex:

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 }
  }
}

Through this approach, both the testability and scalability of the code are improved.

Internal Principles

Here is a complete example:

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 }
}

Pay attention to boundary condition handling, which is critical in production environments.

Business Practice

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.

Performance Comparison

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.

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
• Don't adopt new technology just for the sake of it