Luca Casonato

What if we add a `createHandler(manifest, opts)` function instead? It can just be implemented as follows: ```js export async function createHandler( routes: Manifest, opts: StartOptions = {}, ) { const...

I would rather do this differently. For example by allowing users to return `null` from handlers. Re-interpreting already created `Response` objects with 404 status is not something that will scale...

That works too

> Another option would be to throw a response object for an error page? Not super fond of this path, as `throw` is always very un-optimized in engines and should...

Can you rebase and resolve the conflicts?

Maybe a `targetRoute` parameter on the context would be useful? That would either specify the target "final" route, or if it is an internal request would specify `null` or something....

This is a bug in Fresh. Thanks for reporting!

That is likely a different bug - you are probably importing JSON in the form of `import { foo } from "./data.json" assert { type: "json" }` instead of import...

Yes, i18n will be supported natively at some point (roadmap: #563). But it is not a short term priority, so don't wait for it. If you want something right now,...

I think this bug should be fixed in the latest version of Deno.