cdtut

Also argument validation should be there for example if you pass arguments like `z.string(pattern)` when you meant `z.string().regex(pattern)` it works but should be error saying wrong arguments passed.

### Framework designed error pages Should be possible to set in any way using an API not file based routing. Example `Astro.set404Page(({ props, context }) => Astro.render("ErrorPage.astro", { props, context...

`await astro.renderToString(Component, { props, slots, request, params })` will be possible to use outside of astro so we can use only templating part of astro with any http framework like...

@ematipico Can we use .astro file instead of object in renderToString? So we can use astro instead of other templating languages like liquid and framework like express.

@natemoo-re Would it be so different to support it vanilla Node? How is it out of scope for rendering components in isolation that seems like exactly the case and people...

How to get syntax highlighting in vscode or vim?

@yusukebe `c.get()` doesn't have same benefit. If some routes body need to be transformed and others don't it is inconsistent. Some will have to use `c.get().json` and others use `c.req.json()`...

Can internal `c.req.bodyCache.json = data` have external API like `c.req.setJson(data)` so can be used reliably? For all body requests not just json.

Even with no COREPACK_ENABLE_STRICT the error should not happen if `pnpm --dir` or `yarn --cwd` point to location outside current project.

> can only make trivial assumptions about it Can be trivial if `--dir` is on pnpm or `--cwd` is on yarn then skip warning.