React 17

[birge]

React 17 is around the corner and this package still relies on the unsafe componentWillRecieveProps. I attempted to make a pr to mark it as unsafe but this breaks with pre 16 react versions. Can we move forward and remove support for pre 16 react? If not switching to componentDidUpdate in this PR #14 seems like the logical way forward.

[ljharb]

I'm not sure how accurate "around the corner" is.

As for #14, see #14 (comment).

[balovbohdan]

Do we expect to have React 17 support?

[ljharb]

I do expect to have it.

[mcmxcdev]

Landing here due to incorrect peer dependenciy warnings from yarn install for react and react-dom, would be great to get this resolved!

[ljharb]

@mhatvan they're currently correct warnings.

[balovbohdan]

#32

[balovbohdan]

@balovbohdan thats hostile, untrue, and unnecessary. Everybody cares a lot, which is why we won’t update the peer dep until we’re able to test it. It would be reckless to do so otherwise.

Yep, you're right. But this may be to so complex as expected. React 18 is rather close to getting launched, and folks are still not able to migrate to React 17. It's not correct to go with this warning, as it means dependency is not correct and something may get broken.

[ljharb]

Correct. Your choices remain to stay on react 16, or stop using this library.