Skip to content

Replace Create React App with Vite#605

Closed
benkoppe wants to merge 10 commits into
masterfrom
bek76/vite
Closed

Replace Create React App with Vite#605
benkoppe wants to merge 10 commits into
masterfrom
bek76/vite

Conversation

@benkoppe

@benkoppe benkoppe commented Oct 27, 2025

Copy link
Copy Markdown
Contributor

Summary

This PR replaces CRA (Create React App) with Vite. Builds are significantly faster, especially in development mode, and Vite is generally more extensible and convenient. It also appears to be very useful for PR #604 due to its native typescript support (more testing needed).

This change was very easy to do and appears to have only upsides, so it might be a good idea to go forward with. However, it is also totally unnecessary in general (barring what's mentioned above about its native ts support), so any hesitation is understood.

But it would be nice, because seriously builds are so much faster. For example, wait time on an initial run of npm run start/npm run dev on a new branch went from ~30 seconds to instant.

  • add vite dependencies
  • change files over to vite standards
  • remove create react app dependenices
  • rigorous testing to ensure everything still works

Test Plan

Tests with this change will need to be mostly manual, because Vite intends to work as a mostly transparent replacement for the same things once done by create react app.

Breaking Changes

  • IMPORTANT: In dev mode, we must now type npm run dev rather than npm run start.
  • IMPORTANT: All env variables in .env must be named to replace prefix REACT_APP with VITE
  • I removed some of the frontend scripts, test and eject, as I believe eject is only a create react app thing, and I didn't add Vitest.

@benkoppe benkoppe requested a review from a team as a code owner October 27, 2025 03:07
@CLAassistant

CLAassistant commented Oct 27, 2025

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@benkoppe

benkoppe commented Oct 27, 2025

Copy link
Copy Markdown
Contributor Author

I don't know why the changes to the github workflow are in here. That might need to be addressed.

@benkoppe

benkoppe commented Oct 27, 2025

Copy link
Copy Markdown
Contributor Author

I don't know why the changes to the github workflow are in here. That might need to be addressed.

Seems like I might have accidentally combined this PR with some changes made by @mjaydenkim and @selenaliu1 . Will look into fixing that ASAP.

@dti-github-bot

dti-github-bot commented Oct 31, 2025

Copy link
Copy Markdown
Member

[diff-counting] Significant lines: 6851. This diff might be too big! Developer leads are invited to review the code.

@benkoppe

Copy link
Copy Markdown
Contributor Author

The problems mentioned in the two comments above have been addressed.

Base automatically changed from dka34/changes to master November 2, 2025 21:57
@netlify

netlify Bot commented Mar 4, 2026

Copy link
Copy Markdown

Deploy Preview for carriage-web failed.

Name Link
🔨 Latest commit 56701bf
🔍 Latest deploy log https://app.netlify.com/projects/carriage-web/deploys/69a896305cfc4400085c4090

@vercel

vercel Bot commented Mar 4, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
cu-carriage Ready Ready Preview, Comment Mar 4, 2026 8:30pm

@mjaydenkim

Copy link
Copy Markdown
Contributor

done

@mjaydenkim mjaydenkim closed this Mar 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants