Diogo Cunha

@yoshuawuyts PR updated, only babel transform is missing. @goto-bus-stop and @AndyOGo pushed a few commits replacing `bel` with `nanohtml` on tests. I was doing the same so there might be...

@AndyOGo I rebased already. I have a question: how did you made the `require('nanohtml')` work in tests? Previously `bel` was available to be required because it’s a dep of choo...

@goto-bus-stop that’s it! Thanks

@yoshuawuyts PR updated. The major change here is that transformed code is generated around our `createElement` only instead of `document.createElement` and other auxiliary functions. One single implementation rather than 3...

Very interesting

That makes sense, I also made that with `choo-bundles`, where the browserify plugin is heavily inspired in `split-require`. Unfortunately I needed more than the manifest so I couldn’t just extend...

Not 100% related but you might want to take a look at this: https://github.com/nearform/choo-bundles

I see your point but, in many cases you don't know which data to fetch before render because the route/render-path defines which data will be required. Another typical problem is...

To make it more interesting, async data loading based on a route param with lazy component: ```js const lazyLoadedRoute = async (state, emit) => { const [ component, data ]...

> Both of the examples provided you have the route/render-path before you're asking for the data. The last one doesn't, if you look the `getRouteData` function you'll see that I'm...