@dnolen I know om.next is not ready for tire kicking... but I am seeing "Warning: Don't set .props.omcljs$value of the React component. Instead, specify the correct value when initially creating the element or use React.cloneElement to make a new element with updated props." in the om.dev counter example when it is doing om/commit!

@shaunxcode: not looking for any reports yet really I’m well aware of all the various issues