Skip to content

[Hackathon] Upgrade to React 19 #1584

@rsdmike

Description

@rsdmike

🏆 Hackathon Task: Upgrade to React 19

🔹 Overview

The ui-toolkit-react project is currently running React 18, and we need to upgrade it to React 19 to take advantage of the latest features, optimizations, and bug fixes.

🎯 Task Scope

  • Step 1: Update package.json to use "react": "^19.0.0" and "react-dom": "^19.0.0".
  • Step 2: Update dependencies that might be affected by the React upgrade (react-router-dom, react-query, etc.).
  • Step 3: Check for deprecated APIs or breaking changes in React 19 and refactor code accordingly.
  • Step 4: Run the application and ensure it builds without errors.
  • Step 5: Run existing tests and fix any failing tests caused by the upgrade.
  • Step 6: Perform a manual check of key UI components to ensure they work as expected.
  • (Optional) If applicable, update ESLint/TypeScript configurations for React 19 compatibility.

📂 Relevant Files

  • package.json
  • package-lock.json
  • src/reactjs/{components} (kvm,ider, serialoverlan) (may require updates if React 19 changed lifecycle behavior)

💻 Technical Details

  • Ensure that all dependencies are compatible with React 19.
  • Follow the official React 19 upgrade guide: React 19 Release Notes
  • If a dependency is outdated and incompatible, check if an upgrade is available or consider alternative solutions.

Acceptance Criteria

  • The project builds successfully with React 19.
  • All unit tests pass.
  • No console warnings/errors in development mode.
  • Core UI components function correctly after the upgrade.
  • A PR is submitted with a detailed summary of changes.

🚀 How to Get Started

  1. Comment below to claim this issue.
  2. Fork the repo and create a branch (e.g., feature/react-19-upgrade).
  3. Make necessary upgrades and test thoroughly.
  4. Submit a Pull Request (PR) linking this issue.

📎 Additional Notes

  • Check the CONTRIBUTING.md for coding standards.
  • If you encounter any major breaking changes, document them in the PR description.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Status

    Done

    Status

    Q1 2025

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions