James K Nelson

So basically the way matching works in Navi, is that the remaining part of the route is passed to a `mount()`, which splits it along the first `/` character, ignores...

Thanks :-) I just read through Apollo's SSR docs now so I'm not an expert at this, but one approach would be to pass the `client` into Navi via context,...

Just had a look at the [source](https://github.com/apollographql/react-apollo/blob/master/src/getDataFromTree.ts) of `getDataFromTree()`. It looks like it should work fine with Navi, but you'd need to set up a custom Navi renderer that uses...

Navi state is a little up in the air at the moment. Originally, state was doing some funny things to allow data that was fetched on the server to be...

The issue with hooks is that `useEffect()` is not designed to be run on the server, so for SSR, you need a non-React way to fetch your initial data. One...

@lookfirst the main reason you'd use `getData()` is if you're doing SSR. In this case, you want the data to be available before the initial render, so at least the...

Sorry about the long delay on answering this issue. I'm currently thinking of moving away from navi-scripts long term. It's really a massive hack, and my recent work on https://github.com/jamesknelson/create-react-app/tree/universal-react-scripts...

When using Navi for static rendering, navi-scripts will hook into jsdom's loading code and record JavaScript and CSS files. It then provides these via a `dependencies` object to the renderPageWithString()...

To add to this, it *would* be possible to get 90% support for this in SSR apps -- you'd just have to do a static rendering pass when building the...

So one of the key design constraints for Navi is that each matcher should be able to run independently of the previous matchers, so that they can run simultaneously. The...