In day-to-day development, Vue 3.4 Vapor Mode Preview is being used more and more frequently. This article systematically explains its usage, principles, and optimization strategies.
Quick Start
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.
Internal Principles
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.
Business Practice
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.
Performance Comparison
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
- 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
- Code examples are for reference only and need to be adjusted according to your business scenario