安裝 Vite 及插件并創(chuàng)建配置文件；2. 更新 index.html 指向模塊化入口；3. 調(diào)整入口文件使用現(xiàn)代 ES 模塊語法；4. 替換 package.json 中的腳本為 Vite 命令；5. 靜態(tài)資源處理方式保持不變；6. 將環(huán)境變量前綴從 REACT_APP_ 改為 VITE_ 并通過 import.meta.env 訪問；7. 清理無用依賴和配置。遷移過程簡(jiǎn)單快捷，無需重寫代碼，可顯著提升開發(fā)體驗(yàn)和構(gòu)建性能，推薦所有 CRA 用戶升級(jí)。
Migrating from Create React App (CRA) to Vite is becoming a popular move for React developers looking for faster builds, quicker hot module replacement (HMR), and a more modern development experience. While CRA served the community well, Vite’s speed and flexibility make it an attractive alternative. The good news: the migration is straightforward and doesn’t require rewriting your entire app.
Here’s a practical guide to help you switch smoothly.
? Why Migrate to Vite?
Before jumping into steps, it helps to know why you’re doing this:
- Faster startup and HMR: Vite uses native ES modules and serves code on-demand, so your dev server starts in under a second.
- Better build performance: Uses Rollup under the hood, often resulting in smaller, optimized bundles.
- Modern tooling by default: Built-in support for TypeScript, JSX, CSS modules, and more—without config bloat.
- Active development: Vite is actively maintained and embraced by the broader ecosystem (React, Vue, Svelte, etc.).
If your CRA app feels sluggish during development or build times are growing, Vite is a solid upgrade.
? Step-by-Step Migration Guide
1. Install Vite and Required Plugins
Start by adding Vite and the React plugin:
npm install --save-dev vite @vitejs/plugin-react
If you're using TypeScript, you likely already have it — Vite supports it out of the box.
Create a vite.config.js file in your project root:
// vite.config.js
import { defineConfig } from 'vite';
import react from '@vitejs/plugin-react';
export default defineConfig({
plugins: [react()],
server: {
port: 3000,
open: true,
},
});This config sets up React support and mirrors CRA’s default dev server behavior.
2. Update Your index.html
Move your public/index.html to src/ (optional but cleaner), or keep it in public. Then make sure it has a root element and a script tag pointing to your main React file:
<!-- public/index.html -->
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<title>Your App</title>
</head>
<body>
<div id="root"></div>
<script type="module" src="/src/main.jsx"></script>
</body>
</html>Note: The type="module" and src="/src/main.jsx" are key. Vite serves files from the root, so this works.
3. Adjust Your Entry File (main.jsx or index.js)
Rename or update your entry file (usually src/index.js) to use modern imports and ensure it’s compatible with native ES modules.
// src/main.jsx
import React from 'react';
import ReactDOM from 'react-dom/client';
import App from './App';
ReactDOM.createRoot(document.getElementById('root')).render(
<React.StrictMode>
<App />
</React.StrictMode>
);Make sure you’re using react-dom/client for React 18 .
Also, update file extensions if needed — Vite handles .jsx, .tsx, .js, .ts seamlessly.
4. Update package.json Scripts
Replace CRA scripts with Vite equivalents:
"scripts": {
"dev": "vite",
"build": "vite build",
"preview": "vite preview"
}Now you can run:
npm run dev
And your app should load on http://localhost:3000.
5. Handle Static Assets and Public Files
- Anything in
public/is served at the root (e.g.,/robots.txt,/favicon.ico) — same as CRA. - Use absolute paths in your code:
src="/logo.png"works ifpublic/logo.pngexists. - For dynamic imports or assets inside
src/, useimport asset from './assets/file.png'— Vite processes these.
No major changes needed here.
6. Environment Variables
Vite uses a different convention:
- Prefix environment variables with
VITE_to expose them. - Access via
import.meta.env.VITE_SOMETHING.
Example:
// .env VITE_API_URL=https://api.example.com
// In your code const apiUrl = import.meta.env.VITE_API_URL;
Update any process.env.REACT_APP_* references to use import.meta.env.VITE_*.
7. Optional: Clean Up and Optimize
- Remove
react-scripts:npm uninstall react-scripts
- Delete
src/serviceWorker.js,src/setupTests.jsif unused. - Consider removing
node_modulesand reinstalling withnpm installto avoid conflicts.
You can also add @vitejs/plugin-react-refresh if you want fine-grained HMR control, but @vitejs/plugin-react (which uses Babel) is usually sufficient.
? Test the Migration
- Run
npm run dev— does the app load? Are components updating on save? - Run
npm run build— does it generate files indist/? - Run
npm run preview— test the production build locally. - Check environment variables, API calls, and routing (especially if using
BrowserRouter).
Fix any import path issues or missing extensions (e.g., use .js in imports if unclear).
?? Common Gotchas
Missing file extensions in imports: Vite enforces explicit extensions for
.jsfiles in some cases. You may need to add.jsor.jsxin import statements.Babel config ignored: If you relied on custom Babel plugins, you’ll need to configure
@vitejs/plugin-reactto use Babel, or switch to SWC viavite-plugin-react-swc.Proxy setup: If you used
proxyinpackage.json, move it tovite.config.js:server: { proxy: { '/api': 'http://localhost:5000', }, }
? Final Thoughts
Migrating from CRA to Vite is low-risk and high-reward. Most apps transition in under an hour. You keep your code, get faster tooling, and future-proof your setup.
Bottom line: If you’re still on CRA, now’s a great time to make the switch. Vite delivers a noticeably better developer experience — and your future self will thank you during long coding sessions.
Basically, just install Vite, tweak config and scripts, fix env vars, and go.
以上是從創(chuàng)建React應(yīng)用到Vite：遷移指南的詳細(xì)內(nèi)容。更多資訊請(qǐng)關(guān)注PHP中文網(wǎng)其他相關(guān)文章！
熱AI工具
Undress AI Tool
免費(fèi)脫衣圖片
Undresser.AI Undress
人工智慧驅(qū)動(dòng)的應(yīng)用程序，用於創(chuàng)建逼真的裸體照片
AI Clothes Remover
用於從照片中去除衣服的線上人工智慧工具。
Clothoff.io
AI脫衣器
Video Face Swap
使用我們完全免費(fèi)的人工智慧換臉工具，輕鬆在任何影片中換臉！
熱門文章
熱工具
記事本++7.3.1
好用且免費(fèi)的程式碼編輯器
SublimeText3漢化版
中文版，非常好用
禪工作室 13.0.1
強(qiáng)大的PHP整合開發(fā)環(huán)境
Dreamweaver CS6
視覺化網(wǎng)頁開發(fā)工具
SublimeText3 Mac版
神級(jí)程式碼編輯軟體(SublimeText3)
React與Vue：Netflix使用哪個(gè)框架？
Apr 14, 2025 am 12:19 AM
NetflixusesAcustomFrameworkcalled“ Gibbon” BuiltonReact，notReactorVuedIrectly.1）TeamSperience：selectBasedonFamiliarity.2）ProjectComplexity：vueforsimplerprojects：reactforforforproproject，reactforforforcompleplexones.3）cocatizationneedneeds：reactoffipicatizationneedneedneedneedneedneeds：reactoffersizationneedneedneedneedneeds：reactoffersizatization needefersmoreflexibleise.4）
React的生態(tài)系統(tǒng)：庫，工具和最佳實(shí)踐
Apr 18, 2025 am 12:23 AM
React生態(tài)系統(tǒng)包括狀態(tài)管理庫（如Redux）、路由庫（如ReactRouter）、UI組件庫（如Material-UI）、測(cè)試工具（如Jest）和構(gòu)建工具（如Webpack）。這些工具協(xié)同工作，幫助開發(fā)者高效開發(fā)和維護(hù)應(yīng)用，提高代碼質(zhì)量和開發(fā)效率。
Netflix的前端：React（或VUE）的示例和應(yīng)用
Apr 16, 2025 am 12:08 AM
Netflix使用React作為其前端框架。 1)React的組件化開發(fā)模式和強(qiáng)大生態(tài)系統(tǒng)是Netflix選擇它的主要原因。 2)通過組件化，Netflix將復(fù)雜界面拆分成可管理的小塊，如視頻播放器、推薦列表和用戶評(píng)論。 3)React的虛擬DOM和組件生命週期優(yōu)化了渲染效率和用戶交互管理。
反應(yīng)：JavaScript庫用於Web開發(fā)的功能
Apr 18, 2025 am 12:25 AM
React是由Meta開發(fā)的用於構(gòu)建用戶界面的JavaScript庫，其核心是組件化開發(fā)和虛擬DOM技術(shù)。 1.組件與狀態(tài)管理：React通過組件（函數(shù)或類）和Hooks（如useState）管理狀態(tài)，提升代碼重用性和維護(hù)性。 2.虛擬DOM與性能優(yōu)化：通過虛擬DOM，React高效更新真實(shí)DOM，提升性能。 3.生命週期與Hooks：Hooks（如useEffect）讓函數(shù)組件也能管理生命週期，執(zhí)行副作用操作。 4.使用示例：從基本的HelloWorld組件到高級(jí)的全局狀態(tài)管理（useContext和
React的未來：Web開發(fā)的趨勢(shì)和創(chuàng)新
Apr 19, 2025 am 12:22 AM
React的未來將專注於組件化開發(fā)的極致、性能優(yōu)化和與其他技術(shù)棧的深度集成。 1)React將進(jìn)一步簡(jiǎn)化組件的創(chuàng)建和管理，推動(dòng)組件化開發(fā)的極致。 2)性能優(yōu)化將成為重點(diǎn)，特別是在大型應(yīng)用中的表現(xiàn)。 3)React將與GraphQL和TypeScript等技術(shù)深度集成，提升開發(fā)體驗(yàn)。
React的前端開發(fā)：優(yōu)勢(shì)和技術(shù)
Apr 17, 2025 am 12:25 AM
React的優(yōu)勢(shì)在於其靈活性和高效性，具體表現(xiàn)在：1)組件化設(shè)計(jì)提高了代碼重用性；2)虛擬DOM技術(shù)優(yōu)化了性能，特別是在處理大量數(shù)據(jù)更新時(shí)；3)豐富的生態(tài)系統(tǒng)提供了大量第三方庫和工具。通過理解React的工作原理和使用示例，可以掌握其核心概念和最佳實(shí)踐，從而構(gòu)建高效、可維護(hù)的用戶界面。
了解React的主要功能：前端視角
Apr 18, 2025 am 12:15 AM
React的主要功能包括組件化思想、狀態(tài)管理和虛擬DOM。 1)組件化思想允許將UI拆分成可複用的部分，提高代碼可讀性和可維護(hù)性。 2)狀態(tài)管理通過state和props管理動(dòng)態(tài)數(shù)據(jù)，變化觸發(fā)UI更新。 3)虛擬DOM優(yōu)化性能，通過內(nèi)存中的DOM副本計(jì)算最小操作更新UI。
React和前端開發(fā)：全面概述
Apr 18, 2025 am 12:23 AM
React是由Facebook開發(fā)的用於構(gòu)建用戶界面的JavaScript庫。 1.它採用組件化和虛擬DOM技術(shù)，提高了UI開發(fā)的效率和性能。 2.React的核心概念包括組件化、狀態(tài)管理（如useState和useEffect）和虛擬DOM的工作原理。 3.在實(shí)際應(yīng)用中，React支持從基本的組件渲染到高級(jí)的異步數(shù)據(jù)處理。 4.常見錯(cuò)誤如忘記添加key屬性或不正確的狀態(tài)更新可以通過ReactDevTools和日誌調(diào)試。 5.性能優(yōu)化和最佳實(shí)踐包括使用React.memo、代碼分割和保持代碼的可讀性與可維
