Chore: Update Project Dependencies to Latest Versions (React 19, TailwindCSS 4.1.11, etc.)

[purnasth]

Update Project Dependencies to Latest Versions (React 19, TailwindCSS 4.1.11, etc.)

Summary

Update all dependencies and devDependencies in the project to their latest versions, including major upgrades such as React 19 and TailwindCSS 4.1.11. Ensure the project remains functional and compatible with the new versions.

Tasks

1. Update all dependencies and devDependencies

   • Use pnpm up --latest to upgrade all packages in package.json to their latest versions.
   • Confirm that the following major packages are updated:
     • react to v19.x
     • react-dom to v19.x
     • tailwindcss to v4.1.11
     • @tailwindcss/vite to v4.1.11
     • @tailwindcss/postcss to v4.1.11
     • react-router-dom to v7.6.3
     • react-icons to v5.5.0
     • All other dev tools (eslint, prettier, vite, typescript, etc.) to their latest versions

2. Test the application

   • Run pnpm install and pnpm run dev to ensure the app starts without errors.
   • Check for any breaking changes or warnings in the console, especially related to React 19 and TailwindCSS 4.
   • Review the UI and core functionality for any issues.

3. Update code for React 19 compatibility

   • Review all usage of React APIs, hooks, and lifecycle methods for compatibility with React 19.
   • Refactor code to use new React 19 features where appropriate (e.g., Actions, new hooks, Suspense changes, etc.).
   • Remove or update any deprecated patterns or APIs from React 18.
   • Test for new warnings or errors introduced by React 19 and address them.
   • Consult the official React 19 migration guide and release notes for breaking changes and best practices.
   • Update documentation (README, comments) to reflect the new versions and any required migration steps.

References

• React 19 Release Notes
• TailwindCSS v4.1.11 Release Notes
• pnpm documentation

Acceptance Criteria

• All dependencies are at their latest versions.
• The application builds and runs without errors.
• No breaking changes or regressions in core functionality.
• Documentation is up to date.

Screenshot

---

Note: Major upgrades (like React 19) may require code changes. Test thoroughly and consult official migration guides if needed.