Compatibility with React 18?
See original GitHub issueComponents are not compatible with React 18 as it can be seen in package-lock.json:
"peerDependencies": {
"react": "^16.8.0 || 17.x",
"react-dom": "^16.8.0 || 17.x"
}
Eslint throws warnings, but shows 0 vulnerabilities and I haven’t had any issue yet.
Is it safe to use Reach UI with React 18? When will you update the libraries? Thank you in advance!
Issue Analytics
- State:
- Created a year ago
- Reactions:65
- Comments:16 (7 by maintainers)
Top Results From Across the Web
React v18.0 – React Blog
In this post, we'll give an overview of what's new in React 18, ... Suspense in React 18 works best when combined with...
Read more >Partial list of React 18 compatible library releases #113 - GitHub
Let's use this discussion to track libraries that are known to be compatible with React 18, or have published a React 18-compatible prerelease....
Read more >React 18 & React Native
tl;dr: The first version of React Native compatible with React 18 is 0.69.0. In order to use the new features in React 18...
Read more >What's Coming In React 18? - How-To Geek
To take advantage of all the features, you'll need to upgrade your project and may encounter some breaking changes. React 18 is still ......
Read more >Everything You Should Know About React 18 | Syncfusion Blogs
Syncfusion React JS UI components will always be compatible with the latest React versions. We will include support for React 18 after it ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I don’t support React 18 just yet. There are a number of things that won’t play well with concurrent rendering or the new StrictMode behavior. I’m going to start going through all of that this weekend and take stock of what all needs to be done to get there.
Please keep in mind that this is a free and open source project, free for you to use, fork, or abandon if it no longer works for you. It is maintained very sparingly at the moment, whenever I have the time. There are no updates at the moment, so do with that what you will.
The best way to move the needle on this issue is by helping me out with tasks noted above. If you don’t have the expertise to jump into the actual code, organizational work (breaking down tasks, managing progress, etc.) is also very helpful. This is a great opportunity to invest in a project you rely on, which is the only way [unfunded] open source work can be sustainable.
(Alternatively, I am available for limited contract work if you want to pay me 😄)
Here is a table of all packages I can use to keep track of what needs to be done. Because we don’t have as much test coverage as I’d like, new tests would be appreciated. We’ll still need manual testing (particularly around keyboard navigation in packages that rely on
descendants
as I’m not entirely confident in that package working smoothly in R18). These should all be tested against what’s on thedev
branch, not the latest release.accordion
alert
alert-dialog
auto-id
checkbox
descendants
dialog
disclosure
dropdown
listbox
machine
menu-button
popover
portal
rect
skip-nav
slider
tabs
tooltip
utils
visually-hidden
window-size
For those who want to help with debugging and development
I suggest starting with the lower-level packages that all other packages depend on. Identifying and fixing issues in packages like
utils
,popover
,portal
anddescendants
will make life much easier on the packages intended for end-user consumption.