classtranscribe / classtranscribe/FrontEnd

React Version Upgrade to V18

Open
#818 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
24
Forks
29
PR merge metrics
No merged PRs in 30d

Description

V16 is still widely used today so we don't need to rush this yet, but 18 improves the rendering experience a lot with batching, prioritization and concurrency as well as providing new Hooks and APIs. Plus, the usual security updates, reduced tech debt and nicer versions of many libraries.

It's been out for quite a while now, so it's quite safe to upgrade but we should probably gradually go from 17 (intended as a stepping stone release) to 18. DvaJS should also be potentially fine here https://github.com/dvajs/dva/pull/2515 ([translated](https://github-com.translate.goog/dvajs/dva/pull/2515?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=en&_x_tr_pto=wapp)), looks like they just recently released support for React 18.

In terms of testing, react testing library can bump up to v14 from v12 (https://www.npmjs.com/package/@testing-library/react?activeTab=versions), and most of our current test harness should work fine from there.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the project's current React, DvaJS, and React Testing Library versions and the existing test harness. Confirm the staged React 17-to-18 path and compatibility with DvaJS; done means the frontend and tests run successfully on React 18 with the testing library upgraded to v14.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
frontend, testing
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.