lots of findDOMNode invariant warnings since 3.8.x release

[occamsraiser]

Hi folks. We've been using this library to power our website tooltips in React for about two years. We use Sentry.io to track front end errors experienced by visitors, and I've noticed a huge uptick in findDOMNode Invariant Violation warnings since we deployed 3.8.x. Can anyone else corroborate? We use findDOMNode in two spots in our codebase and I'm seeing these warnings from most of our pages that have these tooltips on them.

The specific error is "findDOMNode was called on an unmounted component"

[stahlmanDesign]

If you use strict mode, React warns that findDOMNode is deprecated. It is used in react-tooltip and would be good if it were refactored to use the proposed solution of adding "a ref directly to the element you want to reference" — I haven't looked into exactly what to do to fix this:
Warning: findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance of ReactTooltip which is inside StrictMode. Instead, add a ref directly to the element you want to reference.

[stahlmanDesign]

Relates to #331 describing possible solution

[stahlmanDesign]

I tried to refactor my code as per the final solution in this article but I still get the warning. I think react-tooltip needs to be refactored

[aronhelser]

If you want to try fixing react-tooltip, I'll gladly accept a PR!

[nadineshmo]

Any update on this PR? I'm also getting the issue "findDOMNode was called on an unmounted component" raised by the first commenter. Not sure if this PR will fix this, or just the strict mode deprecation warning?

[Andsbf]

I wonder the same @nadineshmo, apparently it only fixes the strict mode thing.

[Andsbf]

thanks for merging it in @aronhelser , will a new tag be released with this change?

[oudia15]

Hi @aronhelser, Has a new tag been released with the fix ?

[wwayne]

🎉 This issue has been resolved in version 3.10.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀