Sean Lynch

@jozsi I've not used react-cosmos myself, and I've mostly been using [react-testing-library](https://github.com/kentcdodds/react-testing-library) over enzyme nowadays (see [react-fetch-component's tests](https://github.com/techniq/react-fetch-component/blob/master/src/Fetch.test.js) for an example). With that said, if you're willing to put in...

I've not used it myself but would be open to trying to support it. I don't envision bringing the dependency in directly, but if we can allow a way to...

@jozsi You could also consider using puppeteer if you need a more full-fledged testing environment (headless chrome) but mocking Autosizer works in this case (and would be faster I would...

Sorry I just haven't had time to review this yet. I did think it was going to take a little bit more than bumping packages though and knew I didn't...

@cvanem I wouldn't want to merge with warnings. If someone sends a PR without errors, I'll definitely merge and cut a release.

@tgrowden That would be great. In my visual repos I've typically just leverage react-storybook but it doesn't catch visual regressions, etc (without manual testing, etc). For my other repos, my...

Currently due to using react-virtualized the height has to be known (to enable windowing), either as an explicit pixel height passed to `menuHeight`, or derived pixel height from the number...

@julioxavierr I've been working on a rewrite that drops react-virtualized support (see #54) and also looking to support customization of the adornments (like clear, see also #36) probably via `React.createContext`...

I use it with OData (via [react-odata](https://github.com/techniq/react-odata/)) and have had good success with it thus far in production. Dropping react-virtualized should fix some issues and open up more capability.

Thanks for the detailed response. I expected to have some differences between the two libraries and have been considering supporting both (kind of how I did within the codesandbox). I...