You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, our handling of React versioning is a little... weird. Here's how we're currently versioning react, react-dom, and the related @types packages in core:
Though guidance is a little thin, so far as I can tell the best practice would be for the minor version of all these packages to match. There's no newer versions of the @types packages yet, so I propose that we roll back react/react-dom to 16.9.x. Also, we should probably use a ~ for the version range of react-dom, instead of ^
The text was updated successfully, but these errors were encountered:
Description
Currently, our handling of React versioning is a little... weird. Here's how we're currently versioning
react
,react-dom
, and the related@types
packages in core:Though guidance is a little thin, so far as I can tell the best practice would be for the minor version of all these packages to match. There's no newer versions of the
@types
packages yet, so I propose that we roll backreact
/react-dom
to16.9.x
. Also, we should probably use a~
for the version range ofreact-dom
, instead of^
The text was updated successfully, but these errors were encountered: