@msafi can you please review and merge? Our CI breaks on any warning and we just React 17 upgrade.

I created a fork that specifies React 17 as a peer dependency. The packages is here

This would be great to have merged in. What's the hold-up with this? This is currently the only package that fails in my build simply because this is missing from the peer dependencies.

Can any maintainer prioritize this issue ?

Would love to see this merged in!

I got bit by this issue today. This is the only 3rd-party package I use in my custom component library, and of course, it's the one that brings the whole thing down.

It would be great if it was merged.

Any reason why this can't be merged if it's been approved? We just added it to our design system and it broke the build.

Please merge.

so, now that this is merged, how to kick off a new version?

@mdeeter I think npm run react:publish

For those who still has this problem, there is a solution, not ideal but works just fine.

Source: https://twitter.com/housecor/status/1528820339026821121?s=20&t=2xbr4sm28xDeZeRDsrsxJw

guys please merge this

Hey guys, please merge this PR it's the only lib that fails in my projects