Bring the mixin back.

Obviously, not everyone is using es6 class syntax with React, and I think as the README points out the discussion about how HOCs should work is not completely formalized. I just feel like the mixin was a better approach than wrapping another component in react-onclickoutside.

[Pomax]

I don’t have to bring anything back, the old versions don’t “go away”, they’re still all available through npm. This is a major version upgrade, because everything changed, so if you don’t want that breaking change, don’t install “the latest” version, but set up your package.json to explicitly use 4.x:

  "dependencies": {
    ...
    "react-onclickoutside": "4.x",
    ...
  }

And voila. Mixin.

But I’m not reintroducing it, Mixins are no longer part of React’s recommendation, the Facebook team has deprecated a ton of them (if you liked the linked state mixin for instance, that’s gone now… and I liked that mixin) and they’re not bringing them back, so there is no value in pretending a mixin still makes sense for code that now targets React 15.

[Pomax]

It feels like with React, you’re kind of stuck with “5 months of pretty awesome new stuff” and then a few weeks of porting to the new version. It can certainly get tiring! =)

And hopefully the next few releases of React can bring some clarity to the “official” way to do HOCs, too.