findDOMNode doesn't work with this as argument

[tldrRD]

I'm getting an Uncaught Error: Unable to find node on an unmounted component. error with this component. It is a strange behaviour as handleClickEvent is attached only when the component is already mounted.

The issue is with findDOMNode(this). For some reason it won't work. Is this the desired behaviour or I am missing something?

I'm running everything with Storybook and styled.components.
React/ReactDOM versions are 16.4.0.

import React, { Component, Children } from 'react';
import PropTypes from 'prop-types';
import { findDOMNode } from 'react-dom';

export default class extends Component {
  static propTypes = {
    children: PropTypes.node,
    onClick: PropTypes.func,
  };

  componentDidMount() {
    document.addEventListener('click', this.handleClickEvent, { capture: true });
  };

  componentWillUnmount() {
    document.removeEventListener('click', this.handleClickEvent, { capture: true });
  };

  handleClickEvent = (event) => {
    const el = findDOMNode(this);
    
    if (
      !this.props.onClick ||
      !el ||
      (event.target instanceof Node && el.contains(event.target))
    ) {
      return;
    }

    this.props.onClick(e);
  };

  render() {
    return this.props.children;
  };
}

[gaearon]

Can you create an isolated fiddle demonstrating this?

[Simek]

I was not able to reproduce this issue. All three logs that I defined appears correctly in console in order this (React class), then HTML node found by findDOMNode and at the end click event passed to children.

Test case that I created do not produce any warnings or errors using 16.4.0 or 16.5.1 versions: https://codesandbox.io/s/7klp1j38rx

Feel free to edit/fork my fiddle and correct it to deliver behavior as mentioned in issue.

[tldrRD]

Sorry for taking so long to answer.

I have tried @Simek's code on codesandbox with some modifications to resemble how I use the component and it worked as intended.

I did not manage to install storybook on codesandbox as I don't use it often. I will try to install storybook and keep you updated if I manage to replicate the issue.

At this point I assume it is a problem with storybook and findDOMNode(this). Maybe something with multiple react instances?

Will keep investigating locally.

[tldrRD]

It was a stupid error on my side, the versions of react and react-dom were different. I am so sorry for making a fuss out of it.