Migration Guide: Dependency Updates

Overview

This document summarizes the dependency update from the previous version to the current one, focusing on core build infrastructure updates: Vite, TypeScript, ESLint ecosystem, TailwindCSS, PostCSS, and Vite plugins.

Node.js Requirement Change

Old: Node.js 20.0.0+
New: Node.js 20.19+ or 22.12+
Reason: Vite 7 requirement for ESM-only distribution
Action: Update local development environment and CI/CD pipelines

Major Version Updates

Vite 5.4.1 → 7.1.4

Default browser target changed to 'baseline-widely-available'
Sass legacy API removed (not applicable to this project)
splitVendorChunkPlugin removed (already using manualChunks)
Added explicit build.target configuration to maintain older browser compatibility

vite-plugin-pwa 0.21.2 → 1.0.3

Workbox updated to 7.3.0
workbox-google-analytics deprecated (GA4 incompatible) - removed from configuration
Maintains complex workbox runtime caching strategies

eslint-plugin-react-hooks 5.1.0-rc.0 → 7.0.1

Now a stable release (no longer RC)

Minor/Patch Updates

TypeScript 5.5.3 → 5.9.3
ESLint ecosystem updates (9.9.0 → 9.39.1)
TailwindCSS 3.4.11 → 3.4.18
PostCSS and Autoprefixer updates
@vitejs/plugin-react-swc 3.5.0 → 4.2.1

Removed Dependencies

@tailwindcss/line-clamp: Built into TailwindCSS core since v3.3, no longer needed as a separate plugin

Configuration Changes

package.json

Updated engines.node to >=20.19.0
All devDependencies updated to latest stable versions per the update plan

vite.config.ts

Added explicit build.target: ['es2020', 'edge88', 'firefox78', 'chrome87', 'safari14'] for browser compatibility
Removed deprecated offlineGoogleAnalytics configuration
Verified workbox type definitions remain compatible

tailwind.config.ts

Removed @tailwindcss/line-clamp import and plugin from plugins array
Line-clamp utilities are now built into TailwindCSS v3.4.18

CI Workflows

No changes needed: both workflows already used node-version: [20.x] which meets Vite 7 requirements

TailwindCSS v4 Migration

Successfully migrated from v3.4.18 to v4.1.16
Updated configuration from JavaScript to CSS-first approach
Changed @tailwind directives to @import "tailwindcss"
Updated PostCSS plugin from tailwindcss: {} to '@tailwindcss/postcss': {}
Removed autoprefixer from PostCSS config (handled automatically in v4)
Removed @tailwindcss/line-clamp (built into v4 core)

Testing Recommendations

Run npm install to ensure clean dependency resolution
Run npm run build to verify production build
Run npm run lint to check for linting errors
Test PWA functionality (service worker, offline mode, caching)
Verify all UI components render correctly
Test authentication flows and API integrations

Rollback Plan

Revert package.json to previous dependency versions
Restore previous versions of configuration files if issues arise
Keep a copy of the old package-lock.json for quick rollback if needed

Phase 2: React Ecosystem & UI Libraries (November 2025)

Overview: Updated React 18.x ecosystem and UI libraries to their latest stable versions, prioritizing backward-compatible updates to avoid breaking changes that would require extensive testing.

Strategic Decisions:

Stayed on current major versions for libraries with breaking changes:
- React Router v6.30.1 (avoided v7 due to package merge, import changes, and future flags)
- recharts v2.12.7 (avoided v3 due to API removals and typing changes)
- react-day-picker v8.10.1 (avoided v9 due to controlled props and className changes)
Skipped unused dependencies:
- Zod v3.23.8 (not used in codebase - no schemas found)
- @hookform/resolvers v3.9.0 (not used - no zodResolver usage found)
Updated to latest stable versions:
- All 30+ Radix UI packages (v1.x and v2.x latest)
- UI utilities: framer-motion, lucide-react, sonner, vaul, embla-carousel-react
- react-hook-form v7.65.0 (minor update, backward-compatible)
- Type definitions: @types/react v18.3.12, @types/react-dom v18.3.5

Updated Dependencies:

Radix UI Primitives (all backward-compatible):

@radix-ui/react-accordion: 1.2.0 → 1.2.12
@radix-ui/react-alert-dialog: 1.1.1 → 1.1.15
@radix-ui/react-avatar: 1.1.0 → 1.1.10
@radix-ui/react-checkbox: 1.1.1 → 1.3.3
@radix-ui/react-dialog: 1.1.2 → 1.1.15
@radix-ui/react-dropdown-menu: 2.1.1 → 2.1.16
@radix-ui/react-label: 2.1.0 → 2.1.7
@radix-ui/react-progress: 1.1.0 → 1.1.7
@radix-ui/react-select: 2.1.1 → 2.2.6
@radix-ui/react-tooltip: 1.1.4 → 1.2.8
(and 20+ more Radix UI packages - see package.json for complete list)

UI Utilities & Animation:

framer-motion: 12.5.0 → 12.23.24
lucide-react: 0.462.0 → 0.542.0
sonner: 1.5.0 → 2.0.7
vaul: 0.9.3 → 1.1.2
embla-carousel-react: 8.3.0 → 8.6.0

Forms & Routing:

react-hook-form: 7.53.0 → 7.65.0
react-router-dom: 6.30.0 → 6.30.1

Type Definitions:

@types/react: 18.3.3 → 18.3.12
@types/react-dom: 18.3.0 → 18.3.5

Components Verified:

src/components/ui/form.tsx - react-hook-form v7.65.0 compatible
src/components/ui/calendar.tsx - react-day-picker v8.10.1 (no changes)
src/components/ui/chart.tsx - recharts v2.12.7 (no changes)
src/components/ui/avatar.tsx - @radix-ui/react-avatar v1.1.10 compatible
src/components/ui/label.tsx - @radix-ui/react-label v2.1.7 compatible
src/components/ui/progress.tsx - @radix-ui/react-progress v1.1.7 compatible
src/routes.tsx - react-router-dom v6.30.1 compatible

Breaking Changes Avoided:

React Router v7 (not upgraded):

Would require package merge (react-router-dom → react-router)
Import path changes across 34+ files
Future flags enablement (v7_relativeSplatPath, v7_startTransition, etc.)
Form method normalization (lowercase → UPPERCASE)
Splat route restructuring

react-day-picker v9 (not upgraded):

selected becomes controlled (requires onSelect handler)
Class name changes (day → day_button, day_disabled → disabled, etc.)
Component renames (IconLeft/IconRight → Chevron)
fromDate/toDate → startMonth/endMonth + hidden matchers

recharts v3 (not upgraded):

CategoricalChartState removed
Tooltip typing changes (TooltipContentProps)
activeIndex prop removed
ResponsiveContainer ref shape changed
Z-order now purely render order

Zod v4 (not upgraded - not used):

message → error for customization
String APIs moved to top-level (z.email(), z.uuid(), etc.)
Number validation changes (Infinity no longer valid)
Object defaults behavior changes
Would require codebase-wide schema updates if Zod were used

Testing Recommendations:

Run npm install to ensure clean dependency resolution
Run npm run build to verify production build succeeds
Run npm run lint to check for linting errors
Manually test UI components:
- Forms with validation (react-hook-form)
- Calendar/date pickers (react-day-picker)
- Charts and data visualization (recharts)
- All Radix UI components (dialogs, dropdowns, tooltips, etc.)
- Navigation and routing (react-router-dom)
Test animations and transitions (framer-motion)
Verify icons render correctly (lucide-react)
Test toast notifications (sonner)
Verify drawer/sheet components (vaul)
Test carousels (embla-carousel-react)

Future Considerations:

React Router v7 migration: Plan as a separate task with comprehensive testing
- Enable future flags incrementally in v6
- Test each flag before upgrading to v7
- Update imports across all 34+ files using routing
react-day-picker v9 migration: Plan as a separate task
- Update calendar.tsx with controlled selected prop
- Refactor classNames to new naming convention
- Replace IconLeft/IconRight with Chevron component
- Test date selection and range selection
recharts v3 migration: Plan as a separate task
- Update chart.tsx Tooltip typing
- Test all chart types used in the application
- Verify z-order and layering
- Update any custom chart components
Consider using Zod: If form validation is needed in the future
- Currently not used despite being installed
- Would enable type-safe schema validation
- Integrates well with react-hook-form via zodResolver
- If adopted, plan migration to Zod v4 with codemod assistance

Future Considerations

TailwindCSS v4 migration (separate task requiring extensive testing)
React 19 upgrade (when stable and tested)
Monitoring for Vite 8 and other major updates

Phase 3: Backend Services & Data Management Dependencies (November 2025)

Overview: Updated backend services and data management dependencies with a usage-based approach. After thorough codebase analysis, discovered that 7 out of 9 target dependencies are installed but never used. Updated only the dependencies that are actually imported and used in the codebase.

Strategic Decision: Update Only Used Dependencies

Rationale:

Zero Risk for Unused Code: Can't break what isn't imported or used
Avoid Unnecessary Work: No need to research breaking changes for unused dependencies
Reduce Testing Burden: Updating unused deps adds no value but increases testing surface
Future Cleanup: Unused dependencies should be removed entirely in a separate cleanup task

Dependencies Updated:

Firebase Ecosystem (USED):

firebase: 11.7.1 → 12.5.0
@firebase/analytics: 0.10.13 → 0.11.7
@firebase/auth: 1.9.1 → 1.10.7

Utilities (USED):

tailwind-merge: 2.5.2 → 3.3.1 (REQUIRED for Tailwind v4 compatibility)

Dependencies NOT Updated (Unused in Codebase):

Backend Services:

@supabase/supabase-js: 2.49.1 (no imports found; src/utils/supabase.ts is misleadingly named - only contains localStorage utilities)
@tanstack/react-query: 5.56.2 (no imports found)

AI Services:

@google/generative-ai: 0.24.0 (no imports found)
@google/genai: 0.7.0 (no imports found)

HTTP & Utilities:

axios: 1.8.4 (no imports found)
date-fns: 3.6.0 (no imports found)
next-themes: 0.3.0 (no imports found; custom theme implementation exists in src/contexts/theme.tsx)
web-vitals: 3.5.2 (no imports found)

Breaking Changes Addressed:

Firebase 11 → 12:

Node.js requirement: Minimum Node 20.19+ (already met in package.json engines)
ES2020 target: Firebase 12 uses ES2020 output (verified tsconfig.app.json has ES2020 target)
AI/VertexAI API removal: Not applicable (no AI imports in codebase)
Enum → const map conversion: Not applicable (codebase uses basic Firebase APIs without enum dependencies)
Firestore APIs: All used APIs remain stable:
- getFirestore, collection, doc, setDoc, getDocs, deleteDoc
- query, where, orderBy, limit, startAfter
- writeBatch, enableIndexedDbPersistence
Auth APIs: All used APIs remain stable:
- getAuth, User type, auth method signatures
Analytics APIs: All used APIs remain stable:
- getAnalytics, isSupported, logEvent

tailwind-merge 2 → 3:

Tailwind CSS v4 requirement: Already met (tailwindcss 4.1.16 installed)
No custom config: Project uses default twMerge without custom configuration
No breaking changes affecting usage: The cn utility in src/lib/utils.ts works unchanged
New features automatically supported:
- Important modifier at end of class (e.g., p-4!)
- Arbitrary CSS variable syntax

Files Verified for Compatibility:

Firebase Usage:

src/lib/firebase.ts - Core Firebase initialization (app, auth, analytics, Firestore)
src/contexts/watch-history.tsx - Extensive Firestore operations (CRUD, queries, batches)
src/contexts/auth.ts - Firebase Auth type definitions
src/lib/analytics.ts - Firebase Analytics event tracking
src/lib/analytics-retry.ts - Analytics retry logic
src/lib/analytics-offline.ts - Offline analytics queueing
src/lib/analytics-batch.ts - Analytics event batching

tailwind-merge Usage:

src/lib/utils.ts - cn utility function using twMerge
All UI components in src/components/ui/ - Use cn utility extensively

Package.json Inconsistency Discovered:

During analysis, discovered that several dependencies were already updated beyond previous phase recommendations:

tailwindcss: 4.1.16 (Phase 1 decided to stay on v3, but v4 is installed)
react-router-dom: 7.9.5 (Phase 2 decided to stay on v6, but v7 is installed)
recharts: 3.3.0 (Phase 2 decided to stay on v2, but v3 is installed)
react-day-picker: 9.11.1 (Phase 2 decided to stay on v8, but v9 is installed)
zod: 4.1.12 (Phase 2 decided to skip update, but v4 is installed)

This suggests manual updates occurred. Since Tailwind v4 is installed, tailwind-merge v3 update was mandatory for compatibility.

Testing Recommendations:

Firebase Testing:

Authentication: Test login, signup, Google sign-in, logout flows
Firestore Operations:
- Watch history: Add, update, delete items
- Favorites: Add, remove items
- Watchlist: Add, remove items
- Batch operations: Delete multiple items
Offline Support:
- Disconnect network and perform operations
- Verify operations are queued
- Reconnect and confirm queued operations execute
Analytics:
- Verify events are logged correctly
- Test offline analytics queueing
- Check Firebase console for incoming events
Persistence:
- Test IndexedDB persistence
- Verify data persists across page refreshes
- Test multi-tab scenarios

tailwind-merge Testing:

Class Merging: Test cn utility with conflicting classes
UI Components: Verify all components render correctly
Tailwind v4 Classes: Test any v4-specific utilities
Conditional Classes: Test conditional class application

Future Recommendations:

Dependency Cleanup Task:
- Remove unused dependencies: @supabase/supabase-js, @tanstack/react-query, @google/generative-ai, @google/genai, axios, date-fns, next-themes, web-vitals
- Rename src/utils/supabase.ts to src/utils/local-storage.ts to avoid confusion
- Run npm prune to clean up node_modules
- Update package.json to remove unused deps
Breaking Changes from Manual Updates:
- Document breaking changes from manually updated dependencies (React Router v7, recharts v3, react-day-picker v9, Zod v4)
- Create migration guides for these if issues arise
- Consider reverting to stable versions if breaking changes cause problems
TypeScript Configuration:
- Verify tsconfig.app.json has ES2020 target for Firebase 12 compatibility
- Ensure all TypeScript compilation succeeds
Monitoring:
- Monitor Firebase console for any errors or warnings
- Check browser console for deprecation warnings
- Track analytics event delivery rates

Rollback Plan:

If issues arise with Firebase 12 or tailwind-merge 3:

Revert to previous versions:
- firebase @11.7.1
- @firebase/analytics@0.10.13
- @firebase/auth@1.9.1
- tailwind-merge @2.5.2 (only if reverting Tailwind to v3)
Run npm install to restore previous state
Test that all functionality works
Keep a copy of the old package-lock.json for quick rollback if needed

Phase 4: Build Verification & Testing (November 2025)

Overview: Comprehensive verification and testing plan after completing all three phases of dependency updates (Core Build Infrastructure, React Ecosystem, Backend Services).

Pre-Verification Setup:

Added Missing npm Scripts:
- npm run tsc - TypeScript type checking (required by pr-checks.yml)
- npm run format:check - Check if codebase is formatted correctly with Prettier
- npm run test:coverage - Placeholder for test coverage (no test framework)
- npm run verify - Convenience script running tsc + lint + build
Updated CI Workflows:
- Updated Node.js version to 20.19+ in both workflows
- Fixed TypeScript check command syntax
- Verified continue-on-error flags for optional checks

Step-by-Step Verification Process:

Step 1: Clean Installation

# Remove existing node_modules and lock file
rm -rf node_modules package-lock.json

# Fresh install
npm install

Expected Result: Clean dependency resolution without conflicts or warnings

Step 2: TypeScript Type Checking

npm run tsc

Expected Result: No TypeScript errors. Verify:

ES2020 target compatibility with Firebase 12
All path aliases resolve correctly ( @/, @/hooks/, etc.)
React Router v7 types are compatible
Radix UI component types resolve
No missing type definitions

Step 3: Linting

npm run lint

Expected Result: No ESLint errors. Verify:

ESLint 9.39.1 flat config works correctly
typescript-eslint 8.46.3 rules apply properly
react-hooks/exhaustive-deps warnings are addressed
No unused imports or variables (if rules enabled)

Step 4: Production Build

npm run build

Expected Result: Successful build with no errors. Verify:

Vite 7 builds without errors
All code splitting chunks are generated
Service worker is generated by vite-plugin-pwa
Build output size is reasonable (check dist/ folder)
No warnings about missing dependencies
PWA manifest and icons are copied to dist/

Step 5: Build Preview

npm run preview

Expected Result: Production build serves correctly on http://localhost:4173

Manual Testing Checklist:

Authentication Flows:

Content Browsing:

Search Functionality:

Navigate to /search or use search bar in navbar
Test search with movie titles
Test search with TV show titles
Test search with actor names
Verify search suggestions appear (if implemented)
Test empty search results handling
Verify search results display correctly

Video Player Functionality:

User Profile & Preferences:

Watch History:

Navigate to /watch-history page
Verify watch history displays correctly
Test continue watching cards (ContinueWatchingCard)
Verify watch progress is accurate
Test delete watch history item
Test clear all watch history
Verify Firestore operations work (add, update, delete)

PWA Features:

Firebase Integration:

UI Components (Radix UI):

Routing (React Router v7):

Test navigation between all routes
Verify lazy-loaded pages load correctly
Test dynamic routes (/movie/:id, /tv/:id, /sports/:id)
Test nested routes (/watch/:type/:id/:season/:episode)
Test 404 page (navigate to non-existent route)
Test browser back/forward buttons
Test direct URL navigation (refresh on any route)
Verify ProtectedRoute wrapper works correctly
Test AnalyticsWrapper tracks page views

Responsive Design:

Test on desktop (1920x1080, 1366x768)
Test on tablet (768x1024)
Test on mobile (375x667, 414x896)
Verify mobile menu works (MobileMenu component)
Test touch interactions on mobile
Verify all content is accessible on small screens
Test landscape and portrait orientations

Performance:

Browser Compatibility:

Test on Chrome/Edge (latest)
Test on Firefox (latest)
Test on Safari (latest)
Test on mobile browsers (Chrome Mobile, Safari iOS)
Verify no console errors in any browser
Test service worker support in all browsers

Step 6: Run CI Workflows Locally

Simulate pr-checks workflow:

# Quality checks
npm ci
npm audit || true
npm run tsc
npm run lint
npm run format:check || true
npm run build

# Test coverage (placeholder)
npm run test:coverage || true

# Bundle size analysis
npm install -g source-map-explorer
source-map-explorer 'dist/**/*.js' --json bundle-size.json || true

Expected Result: All checks pass without errors

Step 7: Run Runtime Error Check Workflow

Option A: Trigger workflow manually on GitHub:

Go to GitHub repository > Actions tab
Select "Runtime Error Check" workflow
Click "Run workflow" button
Select branch and run
Monitor workflow execution
Review Playwright report artifact if errors occur

Option B: Run locally with Playwright:

# Install Playwright
npm install -D @playwright/test
npx playwright install --with-deps

# Build and serve
npm run build
npx serve -s dist -l 4173 &

# Wait for server to start
sleep 5

# Create and run Playwright test
echo "const { test, expect } = require(' @playwright/test');

test('no runtime errors on load', async ({ page }) => {
  const errors = [];
  page.on('pageerror', (err) => errors.push('Page error: ' + err.message));
  page.on('console', (msg) => {
    if (msg.type() === 'error') errors.push('Console error: ' + msg.text());
  });
  await page.goto('http://localhost:4173', { waitUntil: 'networkidle' });
  expect(errors, \`Runtime errors found:\n\${errors.join('\\n')}\`).toEqual([]);
});" > runtime-error-check.spec.js

npx playwright test runtime-error-check.spec.js --reporter=list

# Stop server
kill %1

Expected Result: No runtime errors detected on page load

Known Issues & Breaking Changes:

React Router v7 (Manually Updated): The package.json shows react-router-dom @7.9.5 was manually installed, but Phase 2 recommended staying on v6. Potential breaking changes:

Package structure changed (react-router-dom merged into react-router)
Import paths may need updates in 34+ files using routing
Future flags may need to be enabled
Form method normalization changed
If routing issues occur, consider reverting to v6.30.1

recharts v3 (Manually Updated): The package.json shows recharts @3.3.0 was manually installed, but Phase 2 recommended staying on v2. Potential breaking changes:

Tooltip typing changed to TooltipContentProps
activeIndex prop removed
ResponsiveContainer ref shape changed
Z-order now purely render order
If chart rendering issues occur, check src/components/ui/chart.tsx

react-day-picker v9 (Manually Updated): The package.json shows react-day-picker @9.11.1 was manually installed, but Phase 2 recommended staying on v8. Potential breaking changes:

selected prop is now controlled (requires onSelect handler)
Class names changed (day → day_button, day_disabled → disabled)
Component names changed (IconLeft/IconRight → Chevron)
If calendar issues occur, check src/components/ui/calendar.tsx

Zod v4 (Manually Updated): The package.json shows zod @4.1.12 was manually installed, but Phase 2 noted Zod is not used in the codebase. No impact expected since no schemas exist.

Tailwind CSS v4 (Manually Updated): The package.json shows tailwindcss @4.1.16 was manually installed. Phase 1 documented the migration, but verify:

All utility classes work correctly
No class name conflicts
PostCSS configuration uses @tailwindcss/postcss
tailwind-merge v3 is compatible

Troubleshooting:

Build Errors:

Check Node.js version: node --version (must be 20.19+ or 22.12+)
Clear cache: rm -rf node_modules package-lock.json && npm install
Check for TypeScript errors: npm run tsc
Verify all imports resolve correctly

Runtime Errors:

Check browser console for errors
Verify Firebase environment variables are set
Check service worker registration errors
Verify all routes are defined correctly

Firebase Errors:

Verify Firebase config in .env file
Check Firebase Console for project status
Verify Firestore rules allow read/write
Check Firebase Analytics is enabled

PWA Errors:

Check service worker registration in DevTools
Verify manifest.json is valid
Check workbox configuration in vite.config.ts
Verify offline.html exists in public/

Routing Errors (React Router v7):

Check for import path changes (react-router-dom → react-router)
Verify all route components are imported correctly
Check for future flags that need to be enabled
Consider reverting to v6.30.1 if issues persist

UI Component Errors (Radix UI):

Check for prop changes in updated versions
Verify all Radix UI imports resolve
Check for className conflicts with Tailwind v4
Test components in isolation

Success Criteria:

✅ All npm scripts run without errors ✅ TypeScript compilation succeeds ✅ ESLint passes with no errors ✅ Production build completes successfully ✅ All manual tests pass ✅ No runtime errors in browser console ✅ PWA features work correctly ✅ Firebase integration works ✅ All routes navigate correctly ✅ UI components render properly ✅ Responsive design works on all devices ✅ CI workflows pass on GitHub ✅ Lighthouse scores meet targets

Post-Verification Actions:

Document any issues found:
- Create GitHub issues for bugs discovered
- Document workarounds in MIGRATION.md
- Update README.md with known issues
Update documentation:
- Update README.md with new Node.js requirement
- Document new npm scripts
- Update deployment guides if needed
Create rollback plan:
- Keep backup of old package-lock.json
- Document steps to revert if critical issues found
- Tag current commit as "pre-dependency-update" for easy rollback
Future cleanup tasks:
- Remove unused dependencies (Supabase, React Query, axios, date-fns, etc.)
- Install Prettier for code formatting
- Install Vitest for unit testing
- Address breaking changes from manually updated dependencies
- Consider reverting React Router v7, recharts v3, react-day-picker v9 if issues arise

Completion Checklist:

Final Notes:

This dependency update project successfully modernized the codebase from older versions to the latest stable releases. The pragmatic approach of updating only used dependencies and staying on stable major versions (where appropriate) minimized risk while achieving the goal of keeping dependencies current.

Key achievements:

✅ Vite 5 → 7 (major performance improvements)
✅ TypeScript 5.5 → 5.9 (latest features)
✅ ESLint 9.9 → 9.39 (improved linting)
✅ Firebase 11 → 12 (latest Firebase features)
✅ Tailwind CSS 3 → 4 (modern CSS framework)
✅ 30+ Radix UI packages updated (improved accessibility)
✅ All UI utilities updated (framer-motion, lucide-react, sonner, etc.)

The manual updates of React Router v7, recharts v3, and react-day-picker v9 introduce some risk, but comprehensive testing should catch any issues. If problems arise, the rollback plan provides a clear path to revert to stable versions.

Total time investment: ~4-6 hours for all phases including testing and documentation.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Migration Guide: Dependency Updates

Overview

Node.js Requirement Change

Major Version Updates

Vite 5.4.1 → 7.1.4

vite-plugin-pwa 0.21.2 → 1.0.3

eslint-plugin-react-hooks 5.1.0-rc.0 → 7.0.1

Minor/Patch Updates

Removed Dependencies

Configuration Changes

package.json

vite.config.ts

tailwind.config.ts

CI Workflows

TailwindCSS v4 Migration

Testing Recommendations

Rollback Plan

Phase 2: React Ecosystem & UI Libraries (November 2025)

Future Considerations

Phase 3: Backend Services & Data Management Dependencies (November 2025)

Phase 4: Build Verification & Testing (November 2025)

FilesExpand file tree

MIGRATION.md

Latest commit

History

MIGRATION.md

File metadata and controls

Migration Guide: Dependency Updates

Overview

Node.js Requirement Change

Major Version Updates

Vite 5.4.1 → 7.1.4

vite-plugin-pwa 0.21.2 → 1.0.3

eslint-plugin-react-hooks 5.1.0-rc.0 → 7.0.1

Minor/Patch Updates

Removed Dependencies

Configuration Changes

package.json

vite.config.ts

tailwind.config.ts

CI Workflows

TailwindCSS v4 Migration

Testing Recommendations

Rollback Plan

Phase 2: React Ecosystem & UI Libraries (November 2025)

Future Considerations

Phase 3: Backend Services & Data Management Dependencies (November 2025)

Phase 4: Build Verification & Testing (November 2025)