changed lifecycle usages to be react 17 compliant

[s-kem]

Fixes issue referenced in #523

React 16.8 and above throws warnings on usages for these now deprecated methods, and they will be removed in React 17, leaving only the UNSAFE versions

[alexkrolick]

I don't think this is the right solution, since this library is pretty much all side-effects we actually need to be async-safe #509 (comment)

[alexkrolick]

Rewriting it should also fix loads of outstanding issues ;)

[s-kem]

I understand if there's an underlying problem that this isn't addressing, but my understanding here is the UNSAFE tagged functions are exactly equivalent to the originals, resulting in no change in behaviour.

This isn't a proper solution, I'd agree, but it's at least a bandaid to silence the warnings in the current versions of react, and without which this library becomes unusable in React 17.

[alexkrolick]

My point is that it almost certainly will not work with the unsafe methods in React 17, so all this accomplishes is silencing the warnings. Which we can release if you want, but it will still need a rewrite. The UNSAFE_ methods are most unsafe in exactly the ways we are using them now (DOM synchronization side effects).

[fahadahmed]

Hi team,

are there any plans to make the package work with React 17 and hooks? If yes, what are the timelines, if any.

Thanks
Fahad

[alexkrolick]

Closing in favor of #549