Strict Mode Supported

[IceSentry]

Do you want to request a feature or report a bug?

bug

What is the current behavior?

When enabling Strict Mode the console receives a few errors related to using findDOMNode()

What is the expected behavior?

No error in the console when using Strict Mode

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?

React: 16.9
Browser: N/A

Are there any plans to migrate to newer React API's to make Strict Mode work?

[fkhadra]

Hello @IceSentry,

The library don't use findDOMNode directly. This is used by react-transition-group. I'll see if they have any plan to migrate from it.

Thank you

[crobinson42]

When this issue is closed in react-transition-group we can update the dependency version in this lib: reactjs/react-transition-group#559

[fkhadra]

@crobinson42 thank you for linking the issue appreciate

[WPaczula]

There is an updated version of that issue on the react-transition-group: reactjs/react-transition-group#606

[fkhadra]

Thanks @WPaczula

[darklight9811]

Is there a workaround? The toasts won't even display for me.

[ifier]

Still happens :(

[fkhadra]

The guys of react-transition-group are working really hard to address this issue(PR here). This should land soon.

• Strict mode run in development mode only, this should not impact your production code.
• The toast should display even with strict mode @darklight9811
• You should only see a warning with strict mode until the issue is fixed.

Below an example of react-toastify working in strict mode.

[fkhadra]

The new RC of react-toastify support strict mode 🔥. You can install it as follow:
yarn add react-toastify@next or npm i react-toastify@next

I expect to launch the stable release next week if there is no bug.

[fkhadra]

There is a really weird bug when a single notification is displayed the exit transition is not triggered. I'll investigate that bug later

[fkhadra]

Everything has been fixed for strict mode.