Renée
Renée
choo reads state from the `window.initialState` variable, so we can output code for that in bankai.
This happens because bankai tries to server render when you do `module.exports = app.mount('body')`. When server rendering it enters your `view` function and tries to `fetch`, but fetch doesn't exist...
Hmm maybe in Bankai we can use https://www.npmjs.com/package/globals to check if an error message is for an undefined browser global and show a more helpful message about SSR.
I think ideally we would detect that `pushState` was emitted in a route handler and bail out of rendering the current route, then render the new route. I think deferring...
choo hasn't really supported being used in like a "sub application" style but it could be really good for that, so I think any feature that will help it excel...
yeah, knowing the previous route would be really useful!
we could publish an ES module bundle by browserifying `choo/index.js` and adding `export default $BUNDLE`. otherwise we'd have to add ES module support to all dependencies too.
It uses an old version of uglifyify that doesn't support arrow functions. Update to v5 and it works, see remix here: https://glitch.com/edit/#!/cedar-manuscript?path=package.json:14:0
I worry that having Promises arbitrarily deeply in the tree will be a major footgun. for example: ```js async function someElement () { var response = await fetch('/some-data') var data...
Seems good, anything blocking this?