"Breaking out" of TSR/TSS and non-HTML content: how to?

[CynicalBusiness]

Not sure if this is entirely the right place to ask, but Start's docs take me here.

I'm trying to build a small site with TSS to get a good feel for it, and mostly enjoy it, but want to be able to create "semi-static" assets like sitemap.xml and JSON schemas that the user can access.

API routes exist, but they are always prefixed with a base path (usually /api), but some things, namely the sitemap.xml and openapi.json, are expected to be in a very particular place that the API router doesn't cover. However, these are not fully static and can't just be dropped into the public folder. My thinking was to use a "root route" in the API routes (sitemap.xml_.tsx), but this just brings the route up to /api (and doesn't work anyway, as mentioned in #3705)

NextJS makes some special cases for certain files like the sitemap.xml, but allows to "build the server from scratch" and access the underlying Express instance for full control (which is really useful for enabling HTTP2, for example). This isn't a great solution, but at least it's powerful.

I saw some mention of Nitro hooks, but this all looks to be build-time, which doesn't satisfy my use-case.

Is there a way to do this with Start?

[schiller-manuel]

we are currently restructuring API routes so you will be able to use any path as an API route

[CynicalBusiness]

Understood.

Is there a branch/issue/discussion I can keep an eye on for progress?