We're experiencing the same issue!

warning ../node_modules/@reach/auto-id/dist/reach-auto-id.esm.js
Attempted import error: 'useId' is not exported from 'react' (imported as 'useId$1').
warning ../node_modules/@reach/auto-id/dist/reach-auto-id.esm.js
Attempted import error: 'useId' is not exported from 'react' (imported as 'useId$1').

with:

"react": "17.0.2",
"react-dom": "17.0.2"

On the flip side:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: react-volume-viewer@0.3.1
npm ERR! Found: react@18.1.0
npm ERR! node_modules/react
npm ERR!   dev react@"^18.1.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.0 || 17.x" from @reach/listbox@0.17.0
npm ERR! node_modules/@reach/listbox
npm ERR!   @reach/listbox@"^0.17.0" from the root project

It looks like reach 0.17.0 still expects react 16 or 17 even though it relies on react 18 to work. I think the package.json files for each individual component need to be updated. I'm running into issues with

• @reach/listbox
• @reach/tabs

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

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.

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.