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
Some of our projects use React 18, while others like Element Web are stuck on React 17. As long as we need to support React 17, we should enforce in CI that our Compound Web builds stay compatible, because this is delicate to maintain.
Separately, it would also be worth looking into whether there's some less painful way for a component library to support both React versions. Radix Primitives seems to have this figured out? But not sure what their secret to success is.
The text was updated successfully, but these errors were encountered:
Some of our projects use React 18, while others like Element Web are stuck on React 17. As long as we need to support React 17, we should enforce in CI that our Compound Web builds stay compatible, because this is delicate to maintain.
Separately, it would also be worth looking into whether there's some less painful way for a component library to support both React versions. Radix Primitives seems to have this figured out? But not sure what their secret to success is.
The text was updated successfully, but these errors were encountered: