[SlideFade] findDOMNode deprecation warning in StrictMode

Describe the bug findDOMNode warning when using StrictMode (v1 rc.0)

Reproduction: https://codesandbox.io/s/trusting-nightingale-kiij9?file=/src/index.tsx

To see the bug - toggle the animation and see the console.

This is because we don’t use the nodeRef prop when using the react-transition-group (you can read more about the nodeRef prop in the changelog) We can’t really use it without changing the API either, so I can’t really create a good PR to fix it without discussing the API implications with you.

One proposed API is changing the returned function value to include ref as well, changing the API from this

<Fade in={isVisible}>
  {style => <Box style={style} />}
</Fade>

to this:

<Fade in={isVisible}>
  {fadeProps => <Box {...fadeProps} />}
</Fade>

where fadeProps is an object containing the following:

{
  style: style,
  ref: nodeRef,
}

[ljosberinn]

Should be since rc.6 since we use framer-motion internally now!

[ljosberinn]

Looks like the changelog hasn’t been update for RC5, that’s unfortunate. Here’s an excerpt I manually posted on Discord at the time:

1. rc.4 color mode issues should be resolved

2. Checkbox checked icon can be customized via icon prop

3. Node v10 compatibility restored

4. iOS 13 media query list issue fixed

5. ColorModeScript prop for color mode is now called initialColorMode just like in theme.config

6. docs are updated

7. and 4. had issues however, they have been fixed since.