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
Hi, I'm wondering whether the latest version (0.2.x) has a hard dependency on React 17 features or if it would be possible to loosen the peer dependency range to include some version of React 16. From what I could tell, the peer dep was bumped to 17 as part of the cssom commit, but it's not clear to me whether that was a necessary condition.
For context, we want to use Stitches as the styling library for a new internal design system/component library (and Radix for base components). The new components would mostly be used in a greenfield project, but they could also be used in another larger project that is currently targeting 16.14.0. Upgrading to 17 is definitely on the roadmap, but we're not quite ready yet.
Would it be possible to loosen the peer dependency range to include the latest 16.x, even on an "at your own risk" basis? Or is 17 a hard requirement?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, I'm wondering whether the latest version (0.2.x) has a hard dependency on React 17 features or if it would be possible to loosen the peer dependency range to include some version of React 16. From what I could tell, the peer dep was bumped to 17 as part of the cssom commit, but it's not clear to me whether that was a necessary condition.
For context, we want to use Stitches as the styling library for a new internal design system/component library (and Radix for base components). The new components would mostly be used in a greenfield project, but they could also be used in another larger project that is currently targeting 16.14.0. Upgrading to 17 is definitely on the roadmap, but we're not quite ready yet.
Would it be possible to loosen the peer dependency range to include the latest 16.x, even on an "at your own risk" basis? Or is 17 a hard requirement?
Beta Was this translation helpful? Give feedback.
All reactions