Skip to content

Conversation

HatmanStack
Copy link

@HatmanStack HatmanStack commented Sep 10, 2025

Migrate from Create React App to Vite + React 19

What the changes do

Migrates web UI from CRA to Vite, upgrades React 17→19 and Node.js 18→20, fixes all development vulnerabilities.

Why the changes are needed

  • CRA is deprecated and unmaintained
  • Vite provides 10-100x faster builds
  • Development dependencies had security vulnerabilities

Key improvements

  • ⚡ Dev server: <500ms startup vs ~30s
  • 🔒 0 vulnerabilities (was multiple)
  • 🚀 React 19 features (Actions, useOptimistic)
  • 📦 Smaller bundles

Breaking changes

  • Environment variables: REACT_APP_*VITE_*
  • Node.js requirement: 18+ → 20+

Files changed

  • package.json - Dependencies, removed react-scripts conflicts
  • vite.config.js - New build config with JSX support
  • vitest.config.js - Updated to 3.2.4
  • HTML template - Fixed entry point
  • Environment variables across components
  • CloudFormation templates

Testing

✅ 0 vulnerabilities ✅ Builds working ✅ AWS integrations unchanged

Maha Lakshmi Soumya Yalavarthi and others added 11 commits September 8, 2025 20:55
- Add comprehensive WSL setup documentation for Windows developers
- Include step-by-step installation and configuration instructions
- Add troubleshooting guidance and alternative distribution options
- Configure .gitattributes for proper line ending handling
- Change main template rebuild condition from checking specific main component
- Now rebuilds main template whenever any component needs rebuilding
- Improves consistency and ensures main template stays up to date
Simplify main template rebuilding logic in publish.py

See merge request genaiic-reusable-assets/engagement-artifacts/genaiic-idp-accelerator!290
Add Windows development environment setup guide using WSL

See merge request genaiic-reusable-assets/engagement-artifacts/genaiic-idp-accelerator!288
@rstrahan
Copy link
Contributor

Thanks @HatmanStack - this one will take longer to assess, and to be honest might take a while as it doesn't seem to directly address a priority feature gap and is likely to disrupt other in progress features.. I am very curious though, so we'll keep it here and hopefully I can have someone check it out before too much time goes by.

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.

2 participants