James K Nelson

> I guess I overdid myself here haha It's great, I love hearing well thought out opinions 🙌 I see your point about current view data not really being constant...

No idea why this would be happening now. I think you're the second person to come across this, so there's probably something going on. However, it's still working fine for...

So personally, I'd say this isn't a bug in history, but I do agree that it would be nice to solve it within the router. The reason I'd say that...

I'm actually building a Navi app with SSR right now, which I'll probably be open sourcing in a month or two. I'm using [universal-react-scripts](https://github.com/jamesknelson/create-react-app/tree/universal-react-scripts) for the build system, but the...

Hydration happens in an index.js file, whose scripts are added to the rendered HTML. It’s basically just plain Create React App with a special separate index.node.js file. On Sun, Jul...

For what it's worth, you shouldn't have to pass in a request object at all. You can just pass in a URL: ```js /** * The initial URL to match....

I'm curious to see what exactly are you passing into `` or ``?

For reference, here's the relevant part of my `index.js`: ```js let navigation = createBrowserNavigation({ routes, context, }) ReactDOM.render( , node ) ``` I don't touch `window.__NAVI_STATE__` at all.

Suspense is not required, in fact it won't actually work on the server side at all. However, you *will* need to wait for the route to be ready before rendering,...

I think my file above is pretty similar to your `client.js` - it handles hydration, and is separate to `index.node.js` which is what the server calls. The reason you'll need...