惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

WordPress大学
WordPress大学
B
Blog RSS Feed
The GitHub Blog
The GitHub Blog
爱范儿
爱范儿
博客园 - 司徒正美
J
Java Code Geeks
酷 壳 – CoolShell
酷 壳 – CoolShell
Engineering at Meta
Engineering at Meta
大猫的无限游戏
大猫的无限游戏
D
Docker
Blog — PlanetScale
Blog — PlanetScale
Recent Announcements
Recent Announcements
罗磊的独立博客
Microsoft Azure Blog
Microsoft Azure Blog
博客园 - 聂微东
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
人人都是产品经理
人人都是产品经理
Stack Overflow Blog
Stack Overflow Blog
M
MIT News - Artificial intelligence
腾讯CDC
T
The Blog of Author Tim Ferriss
小众软件
小众软件
U
Unit 42
T
Tailwind CSS Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
What Does Vue 3 `ref()` Compile to in React with VuReact?
Ryan John · 2026-05-20 · via DEV Community

Ryan John

VuReact compiles Vue 3 code into standard, maintainable React code. In this article, we will focus on one of the most frequently used Vue APIs: ref() and shallowRef().

If you write them in Vue, what does VuReact turn them into on the React side?

A Quick Note Before We Start

To keep the examples easy to read, this article follows two simple conventions:

  1. All Vue and React snippets show core logic only, with full component wrappers and unrelated configuration omitted.
  2. The discussion assumes you are already familiar with the API and behavior of Vue 3 ref and shallowRef.

Compilation Mapping

Vue ref() -> React useVRef()

ref() is one of the most fundamental reactive APIs in Vue 3, and easily one of the most commonly used in day-to-day development.

Here is the simplest possible example:

  • Vue
<script setup>
import { ref } from 'vue';

// Primitive reactive state
const count = ref(0);
</script>

Enter fullscreen mode Exit fullscreen mode

  • Compiled React
import { useVRef } from '@vureact/runtime-core';

// Compiled into a dedicated Hook that mirrors Vue ref semantics
const count = useVRef(0);

Enter fullscreen mode Exit fullscreen mode

As you can see, Vue's ref() is compiled directly into the React Hook useVRef().

VuReact's useVRef is the runtime adapter for ref. You can think of it as a React-side equivalent of Vue ref, designed to preserve the same mental model and behavior, including reactive updates, .value access, and predictable view re-rendering.

TypeScript Support Stays Intact

In real-world projects, TypeScript is the default rather than the exception. VuReact preserves generic type annotations so React-side type safety and editor hints stay intact.

  • Vue
<script lang="ts" setup>
const title = ref<string>(''); // string
const isLoading = ref<boolean>(false); // boolean
const userList = ref<Array<{ id: number; name: string }>>([]); // array of objects
const config = ref<Record<string, any>>({ theme: 'dark' }); // record type
</script>

Enter fullscreen mode Exit fullscreen mode

  • Compiled React
const title = useVRef<string>('');
const isLoading = useVRef<boolean>(false);
const userList = useVRef<Array<{ id: number; name: string }>>([]);
const config = useVRef<Record<string, any>>({ theme: 'dark' });

Enter fullscreen mode Exit fullscreen mode

No manual type adaptation is required. VuReact keeps the original type annotations so the generated React code remains just as type-safe as the Vue source.

Vue shallowRef() -> React useShallowVRef()

shallowRef() is Vue 3's shallow reactive variant. It is especially useful when you want to react to top-level reference changes without deeply tracking nested properties.

  • Vue
<script setup>
import { shallowRef } from 'vue';

// Only tracks top-level reference changes
const count = shallowRef({ a: { b: 1, c: { d: 2 } } });
</script>

Enter fullscreen mode Exit fullscreen mode

  • Compiled React
import { useShallowVRef } from '@vureact/runtime-core';

// Preserves shallowRef-style shallow reactivity
const count = useShallowVRef({ a: { b: 1, c: { d: 2 } } });

Enter fullscreen mode Exit fullscreen mode

The mapping follows the same pattern: Vue shallowRef() becomes useShallowVRef().

VuReact's useShallowVRef is the runtime adapter for shallowRef. In practice, that means only top-level reference changes trigger updates, while nested property mutations do not. This lines up well with React's update model and is especially helpful for performance-sensitive scenarios involving complex objects.