Ashton

Hey, I can't see any breaking changes in redux-form at a glance that'd make it incompatible with this. However there's a few new features I want to add to this...

Sure, an example would help. If you can show something that worked _before_ v6 & then stopped working that'd be perfect

Oh, you don't need to pass `fields` in, just do: ``` js reduxForm({ form: 'InviteManagerForm', validate: validate(), })(InviteManager) ``` That will validate every field, should work with both v5 &...

I've just pushed a complete rewrite of redux-validate, can you upgrade and see if this issue still affects you?

@ctrlplusb how's the bashing going?

@toxicFork Using `react 15.0.2`, `react-three-renderer 2.0.1` & `chrome 50.0.2661.102`. Also noticed the problem goes away in production mode & other browsers. @imjasonmiller Tempted to say no, I tried setting `NODE_ENV`...

@toxicFork I'll test sometime later this week

I've encountered a variation of this with the `.quiet()` modifier, where this code never prints `'DEBUG'` due to an immediate exit: ```ts try { await Bun.$`cd ${path} && bun link`.quiet();...