Reserved routes

[Aprillion]

Would it be worth to add a mechanism to specify "reserved" routes for internal Remix magic that will never match user code?

I managed to shoot myself in the leg when using CF Workers deployment, when I specified a GH secret with wrong KV namespace id, so my app was deleting the __...-workers_sites_assets namespace instead of the one I wanted to use for dynamic content (whole boring story on https://twitter.com/aprillion0042/status/1588192612619526145 and StampyAI/stampy-ui#84).

I used code like following in routes/$.tsx:

export const loader = async ({params}) => redirect(`/?${params['*']}`)

The combination of the 2 caused my static files like /build/_assets/root-4XJTI7ZZ.css to be redirected to /?build/_assets/root-4XJTI7ZZ.css and I couldn't figure out why it's happening.

If Remix set up /build/_assets/* as a protected (reserved) route for internal use, unreachable by my own code, that would have been a pit of success for me (I would investigate HTTP 404 instead of HTTP 302 with a wrong mime type and would find the root cause sooner).

On the other hand, I understand if some users will want to generate dynamic content for routes like this, there is no 1 size fits all. So I would propose only to have default reserved routes, changeable by the user in "some" configuration file. What do others think?

[sergiodxa]

Remix don't server the static assets like the CSS and client-side JS code by itself.

In Express for example you have to setup express.static to serve files from the public folder before you setup the Remix request handler.

So /build/_assets/* is not really something Remix knows about, if you received a request there is because your server code (Cloudflare Workers in your case) was either not configured correctly or it didn't know about the file and sent the request to Remix.

[Aprillion]

I didn't touch the CF Worker code at all, only Remix. If you say there is a bug in the CF Worker provided by Remix, please open an issue to fix such code in Remix source code.

If you are saying only that Remix doesn't know about static files yet, then my discussion topic is whether Remix should start caring about routes for static files to improve debugging experience. Or if that concern should stay outside of Remix, as currently.