How to handle dynamically created pages in routing?

[OrangeTimes]

I'm creating +Page.js dynamically by fetching them from npm server using vike and Fastify server. When executing a request for the first time it fails with 404. The next request renders the page correctly as expected. As I understand the internal router map is unaware of the newly created page on the filesystem. Here is the log when trying to render /test/[email protected]

4:14:41 PM [vike][request(2)] HTTP request: /test/[email protected]
4:14:41 PM [vike][config] created /test/[email protected]/+Page.js
4:14:41 PM [vike][request(2)] URL /test/[email protected] doesn't match the route of any of your pages:

│ / │ Filesystem Route │ /pages/ │
│ /about │ Filesystem Route │ /pages/about/ │
│ /star-wars │ Filesystem Route │ /pages/star-wars/index/ │
│ /star-wars/@id │ Filesystem Route │ /pages/star-wars/@id/ │
│ /test │ Filesystem Route │ /test/ │
│ /test/[email protected] │ Filesystem Route │ /test/[email protected]/ │

See https://vike.dev/routing for more information about routing.
4:14:41 PM [vike][request(2)] HTTP response /test/[email protected] 404

I have read the documentation on routing in vike but cannot figure out hot to handle this situation

[brillout]

Hm, I wouldn't know what the issue could be. The best would be a minimal reproduction.

[brillout]

What approach would you suggest? How to fetch a page and render it on the go?

It's difficult to say without knowing more about your use case.

I'd suggest to keep trying (alternative approaches), while feel free to create new feature requests where you see fit.

[OrangeTimes]

Is it possible to add a new file route using the route function?

[brillout]

Is it possible to add a new file route using the route function?

I think the docs are pretty clear that this isn't the purpose of Route Functions? See https://vike.dev/route-function.

Maybe a more fruitful discussion would be that you described the fundamental requirement you're trying to fulfill. Is it about scaling your teams? Are you a media agency and it's about some kind of customer requirement?

Your approach is quite unusual, and it's difficult to justify spending time adapting Vike for the peculiar setup of a single user.

[OrangeTimes]

Ok we have a few teams that work on different versions of the same page for A/B experiments and we have many of these experiments running in production simultaneously. The page can have multiple variations, all of which are published to NPM registry as separate isolated packages It allows teams to work independently and also allows us to scale them as well. We have a separate router service that determines in runtime which page the customer should go to based on criteria set in router config and customer request headers like GeoIP and others. Later, the router calls our existing SSR solution to render specific pages and versions and return the pre-rendered content to the customer. We want to modernize our SSR solution (developed more than 8 years ago) and thought that something on the market can already do some stuff we do and do it better and provide more features to us (latest React support, prefetching etc). So far the teams are really happy working in such a setup so we don't want to change things for them. Also, we need a single solution and not like 5 different apps for SSR because we are limited on resources (each team can request multiple copies of the production environment) If we add a lot of apps for SSR we will run out of resources pretty quickly. Also publishing pages in the scope of the SSR app will not work for us because we don't want to redeploy the app multiple times on prod affecting caching. After all, teams can publish a new page or variation of it every hour. So it we need a solution that can be deployed as single instance that can render all our pages on the fly without the need of redeployment to support some new pages.

We have a tested way how to fetch a page on the filesystem on the go using pnpm store, so I was thinking in 2 approaches

• create symlink like /pages/[email protected]/Page+ to pnpm store on the go during the initial request to VIKE. But it seems there is no way to tell Vike about new file route programmatically
• parse bundled page as a string and pass it to PageContext as some custom property. It was working for server rendering, but I didn't manage to make it work during hydration due to different errors on the client

[brillout]

Quickly glazing over your answer, it seems like your only blocker is your hack of mis-using npm packages to re-deploy. AFAICT all your other concerns are usual use cases and can be achieved with Vike and without any quirks.

I'd be happy to help about your other concerns (a lot of what you wrote seem unrelated to the problem of the original post) but I think the best would be some kind of sponsoring or consulting.

Precise, well-written, and well-explained feature request(s) welcome. (Regardless of sponsoring.)