-
Notifications
You must be signed in to change notification settings - Fork 561
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.17.0 does not work with React 17 #921
Comments
We're experiencing the same issue! |
with:
|
On the flip side:
It looks like
I gather there's more components with the same issue though |
Any update on this? Has anyone found a fix? I'm completely unable to use Reach UI in React 17 |
Downgrade the package to 0.16 will restore the previous behavior. |
v0.17 doesn’t work well with React < 18: reach/reach-ui#921
same issue here, it's quite a paradox - the library as a whole can't be used with react 18 yet, but certain sub-components work only with it and don't work anymore with react 17 - or am I missing something? |
make a fix or something that allow a user to use their own useId , or a guide how actually use your library. Reach! youre popular. |
v0.17 doesn’t work well with React < 18: reach/reach-ui#921
🐛 Bug report
Since useId is not available on React17 it breaks with [email protected]
In auto-id package https://github.com/reach/reach-ui/blob/develop/packages/auto-id/src/index.tsx,
import * as React from "react";
is compiled as
import { useId as useId$1, useState, useEffect } from 'react'
in the esm module.
This leads to the following error
The text was updated successfully, but these errors were encountered: