Ayrton

As a workaround I believe we can loosen up the dependency to do `^2.1.0 | ^3.0.0`. See [this diff](https://github.com/algolia/react-element-to-jsx-string/compare/v2.1.0...v3.0.0). We only have [one use case](https://github.com/producthunt/chai-enzyme/blob/f133f1d607d632af4645f9d4971778271d0dabfc/src/assertions/contain.js) with react-element-to-jsx library so far.

@ljharb how do you see the most ideal solution?

I think it's best to pin chai-enzyme to `0.4.2`, which is the latest release that doesn't pull in `react-element-to-jsx-string`. As an aside `react-element-to-jsx-string` supports react [`0.14.8`](https://github.com/algolia/react-element-to-jsx-string/blob/master/package.json#L35) and above while we...

Can you add a test case please

We should probably document this behaviour to avoid any further confusion, any chance you can open a PR @junpos?

Wondering if we should alias this to ```js expect(wrapper).to.have.found('#root') ``` to avoid the confusion

Confirmed this is indeed a bug when the component is mounted (not when using `shallow` or `render`): ``` js class NullFixture extends React.Component { render () { return (hi) }...

Actually according to our passing test suit we have `style` support for each render method. ``` sh #style ✓ (shallow): chains ✓ (mount): chains ✓ (render): chains (name) ✓ (shallow):...

Running your tests on master I get these results: ``` Chai-enzyme style test ✓ (shallow): should do style test on shallow component ✓ (mount): should do style test on shallow...

Will try to release a beta 1.0.0 release tomorrow with support for enzyme 3 (& thus react 16). Once things look stable (I'll test the library against the Product Hunt...