David Barratt

sure! you do have to include the translation strings withing your JavaScript app. In the case of https://github.com/wikimedia/interactiontimeline the build script (webpack) bundles them into the single JavaScript file.

I ended up creating React bindings for this library: https://github.com/wikimedia/InteractionTimeline/tree/master/client/src/components/i18n It can (and probably should) be split out into a separate library. So in the end, I think it would...

I've moved the React bindings into a separate library: https://github.com/wikimedia/react.i18n

AMAZING! I created a few issues for it. I don't see anything major. When it's published on npm I'll put it in https://github.com/wikimedia/react.i18n and see if the tests pass (I...

> Why use getEdgeProps if you want to render on the client? Because I want to have SSR when the URL is directly accessed.

> So basically, you want the first load to be served from cache then, skip getEdgeProps on navigation and run it on the client? > I'm also not a fan...

> Wouldn't it be easier then to do a hard navigation then? I'm sorry, I don't understand your question.

> I propose to perform a hard navigation when user clicks the link. On first load, page will be rendered with getEdgeProps, upon additional navigations to that route, pages will...

errr... let me be more clear. Right now, the behavoir is that if you have `getEdgeProps()` on a route and you navigate to it from a different route, @flareact will...

Some other users cases in vercel/next.js#11897 are when you already have the props locally for the page transition and there is no need to make an XHR request to get...