React 18 support in peerDeps

[Chupriarti]

Is it possible to update peerDependencies for React 18 support?

[agilgur5]

Unfortunately it's not quite as simple as updating a peerDep as the devDep and testing suite has to be updated as well.
Per #64 (review) , the whole test harness basically has to be rewritten as Enzyme was never fully updated to support React 17, let alone React 18

[Chupriarti]

Thank you for your reply.
So I guess this issue can be close, until other code will be updated.

[agilgur5]

No, it should remain open as it is an existing and relevant issue. In particular, it would be good to see how many upvotes it garners compared to other issues/features/etc in order to help measure priority

[Rick83600]

Need the update of peerDependencies React 18 please

[LJGrant]

Any chance that is is being worked on? If so, any eta on when this might be resolved?

[agilgur5]

Any chance that is is being worked on?

There is a label that indicates whether something is being worked on.
Otherwise, please see this blog post written by popular OSS author sindresorhus and inspired by ESLint author nzakas.

If so, any eta on when this might be resolved?

If you (and your company) need this quickly, you are more than welcome to contribute. I am a volunteer working on this in my limited free time and on top of that, am spread pretty thin amongst several OSS projects.

As I've outlined above already, please see #64 (review) for what that entails:

1. rewriting the test harness with RTL and react-dom-instance
2. making sure all tests still pass and that such a refactor is actually compatible (part of the complexity is the unknown)
3. then upgrading to React 18 in peer and devDeps
4. and finally ensuring the tests pass and fixing anything that may have broken in React 18 (another unknown)
5. (optional) adding a test for concurrent mode, while it is off by default, would also help with forward compatibility.

I believe the example and the "Usage" section of the docs need updating to createRoot etc.
Not sure if anything else will break; off the top of my head if React 17's JSX is required in React 18, this actually might require a breaking change (since it is currently compatible down to React 14)