Rom
If doing pre-rendering only is an option (i.e. without using SSR) then I'd recommend doing that.
👍 Keep me updated.
👍 I'm glad it worked out. Btw. in case your company is up for it: https://github.com/sponsors/brillout – sponsoring is starting to make a big impact on VPS.
I'm actually almost done with it at https://github.com/vikejs/vike/tree/brillout/feat/vike-config. I've updated https://github.com/vikejs/vike/labels/contribution-welcome%20%3Atwo_hearts%3A.
Actually, in general, I'm thinking the best is to do both: merge *everything* into `pageContext` while providing a `pageContext.from`. See https://github.com/vikejs/vike/issues/1268.
Hello Kenzo, we're actually already working on at it https://github.com/vikejs/vike/pull/1342. Contribution much welcome for other https://github.com/vikejs/vike/labels/contribution-welcome%20%3Atwo_hearts%3A tickets 💯
I stand to be corrected, but I believe that isn't possible. The idea is to have VPS code-gen `type Routes = '/product/${string}' | '/' | '/some-other-route'` while: - `Routes` is...
From Discord: > It would be very nice if it were possible to auto-generate types for routes out of the box, to be able to do something like `
Currenlty, i18n is being implemented programmatically, which provides a lot of flexibility, see https://vite-plugin-ssr.com/i18n. And, yes, for typesafe links a declarative i18n interface will be needed. (Not only for providing...
> Would this also apply to navigate? Yes.