Open
Bug 1774344
Opened 2 years ago
Updated 1 year ago
[meta] Upgrade to React 18
Categories
(DevTools :: General, task)
DevTools
General
Tracking
(Not tracked)
NEW
People
(Reporter: Honza, Unassigned)
References
(Depends on 11 open bugs)
Details
(Keywords: meta)
React Upgrade Roadmap
- Migrate Enzyme tests to RTL
- Asking Julien and Greg to review first couple of migrated tests and provide feedback
- We might use help of existing contributors if possible (first-good-bugs)
- Migrated perhaps even some Mocha tests (if there is time)
- Upgrade React-Redux to 8.0.1
- There should be no breaking changes
- Fix React Warnings
- They become errors in 17
- Upgrade to React 17
- Minimum changes in this version, but there are some breaking changes
- Chunking the upgrade helps to keep the work size and regressions down
- We are using multiple providers/stores, which might introduce some difficulties
- Upgrade to React 18.x
- Breaking changes ("asynchronous rendering") but we don’t have to use it.
- Keep using “ReactDOM.render” (not the new “ReactDOM.createRoot”)
Honza
Reporter | ||
Comment 1•2 years ago
|
||
Adding existing (and related) bug reports as dependencies.
Comment 2•2 years ago
|
||
(In reply to Jan Honza Odvarko [:Honza] (always need-info? me) from comment #0)
- Upgrade to React 18.x
- Keep using “ReactDOM.render” (not the new “ReactDOM.createRoot”)
The latest version of react-testing-library uses ReactDOM.createRoot()
internaly instead of ReactDOM.render()
.
Thus we can switch to use ReactDOM.createRoot()
after we complete to migrate to update to v18 and react-testing-library safely.
React v18 still supports ReactDOM.render()
but it's warned as deprecated in react-dom development build and recommend to switch to ReactDOM.createRoot()
. I think we don't have to keep to use ReactDOM.render
.
Updated•1 year ago
|
Summary: [meta] React Upgrade → [meta] Upgrade to React 18
You need to log in
before you can comment on or make changes to this bug.
Description
•