Tim Branyen

sure does! i'm looking into a few issues with this.

Interesting I have reproduced this as well.

+1 been wanting this for a long time

NPM is having consistency issues ATM. Published 0.5.0, but NPM reports 0.4.0 as latest. I'll try again later in the day.

Looks like I broke some tests with the latest promisify-node. I'll work on addressing these, once NodeGit builds on Node 10.

I guess this didn't solve shit. Back to the drawing board...

Changing the folder structure will be a rebase nightmare as previously outlined. I don't see a huge rush to bring this in immediately, but I'll try and review this weekend!...

I believe this is also causing a problem with the patching layer, as it is looking for previously defined nodes that no longer exist: 

This seems to specifically affect nested components only.

React hooks: - [ ] [useState](https://reactjs.org/docs/hooks-reference.html#usestate) - [ ] [useEffect](https://reactjs.org/docs/hooks-reference.html#useeffect) - [ ] [useContext](https://reactjs.org/docs/hooks-reference.html#usecontext) - [ ] [useReducer](https://reactjs.org/docs/hooks-reference.html#usereducer) - [ ] [useCallback](https://reactjs.org/docs/hooks-reference.html#usecallback) - [ ] [useMemo](https://reactjs.org/docs/hooks-reference.html#usememo) - [ ] [useRef](https://reactjs.org/docs/hooks-reference.html#useref)...