inland jay
https://docs.astro.build/en/guides/routing/#dynamic-routes
If I want to have i18n route, I will have to accept losing http://example.com/favicon.svg route. I prefer to keep an exception for all static files in /public directory. Is there any option to help me archive this?
whole perchBOT
Hi @inland jay. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
To address your concern about preserving static asset routes while implementing i18n dynamic routes in Astro, there are a couple of approaches you can consider:
routes.extend option:The Astro Cloudflare adapter provides a routes.extend option that allows you to exclude specific routes from being processed by dynamic routing. You can use this to preserve your static asset routes. Here's an example configuration:
export default defineConfig({
adapter: cloudflare({
routes: {
extend: {
exclude: [{ pattern: '/favicon.svg' }, { pattern: '/public/*' }],
}
},
}),
});
This configuration would exclude the /favicon.svg route and all routes under /public/ from being processed as dynamic routes, preserving their static nature Cloudflare Adapter Documentation (https://docs.astro.build/en/guides/integrations-guide/cloudflare/#routesextend).
experimental.globalRoutePriority flag:Astro 4.2.0 introduced an experimental feature that allows for more control over routing priorities. By enabling this flag, you can ensure that file-based routes (including static assets) are prioritized equally with dynamic routes. This might help in preserving your static asset routes:
export default defineConfig({
experimental: {
globalRoutePriority: true
},
// ... other configuration options
});
This experimental feature allows for more flexibility in route prioritization Configuration Reference (https://docs.astro.build/en/reference/configuration-reference/#experimentalglobalroutepriority).
If you need more fine-grained control, you can use the routing: "manual" option in your i18n configuration. This disables Astro's built-in i18n middleware, allowing you to implement your own custom routing logic that can prioritize static assets:
export default defineConfig({
i18n: {
defaultLocale: "en",
locales: ["en", "fr", "pt-br", "es"],
routing: {
manual: true
}
}
});
With this approach, you would need to implement your own routing logic to handle both i18n and static assets Internationalization Guide (https://docs.astro.build/en/guides/internationalization/#manual).
It's worth noting that the public/ directory in Astro is designed for static assets that should be served as-is, without processing Project Structure Documentation (https://docs.astro.build/en/basics/project-structure/#public). In theory, these should not be affected by dynamic routing, but if you're experiencing issues, the above approaches should help you maintain control over your static asset routes.