Support React 19 in Component Testing

[jennifer-shehane]

What would you like?

React 19 Beta is out: https://react.dev/blog/2024/04/25/react-19-upgrade-guide

Why is this needed?

No response

Other

No response

[AtofStryker]

support spike for react 19 is done and implemented here. Once React 19 releases, we can revisit this and get the feature shipped out to support react 19 CT fairly quickly.

[boylec]

AFAIK React 19 is in RC status.

Any ideas about when this support within cypress is going to be released?

[AtofStryker]

AFAIK React 19 is in RC status.

Any ideas about when this support within cypress is going to be released?

@boylec We are waiting for Raact to release version 19 as generally available. Most of the implementation work for this is done on our end, so the turnaround should be short.

[boylec]

@AtofStryker thanks for the heads up.

We are relying on some juicy features in the Next.JS 15 RC (and hence React 19 RC by indirect dependency) in production.

Any chance you guys might consider providing a path for us bleeding edge fanatics to be able to use cypress for component testing against these versions considering the work is mostly done as you mentioned?

[AtofStryker]

@AtofStryker thanks for the heads up.

We are relying on some juicy features in the Next.JS 15 RC (and hence React 19 RC by indirect dependency) in production.

Any chance you guys might consider providing a path for us bleeding edge fanatics to be able to use cypress for component testing against these versions considering the work is mostly done as you mentioned?

Hey @boylec . Sorry for the late reply. A lot going on 😅 . Currently at this time we don't have a mechanism planned to have release candidates of the component testing versions generally available. It gets a bit difficult since the component testing harnesses ship with the app and the waters could get muddy between what is breaking and what isn't.

What I can say is that the React 19 testing harness really does not differ almost at all from the React 18 harness, so you could leverage that for now and ignore the dependency warnings. However, if more features are added or changed (for example, angular signals or something else that impacts the harness), we can discuss making a binary readily available.