Pooya Parsa

it might be an issue but please reopen with reproduction 🙏🏼

how it makes an issue with your external usage? (again, i understand it is an issue, but in order to track any issue report, this is expected, otherwise i have...

@kricsleo i think we can set it to something like `10` to make setup easier. Feel free to drop a PR 👍🏼

Thanks for opening the discussion (and for the draft PR). I understand there are use cases in which we need to have access to available handlers/route patterns. We cannot export...

Also, checking https://github.com/artmizu/nuxt-prometheus/issues/48, actually you can already access to the runtime matched route pattern. ```ts export default defineNitroPlugin((nitroApp) => { nitroApp.hooks.hook('beforeResponse', (event, { body }) => { console.log(event.method, event.path, event.context.matchedRoute);...

I agree that multi headers is a headache. Node.js already does process by joining with `; ` ([src](https://github.com/nodejs/node/blob/a072ec382f8b8a2e2e90e2520c1b94a668b4bc3b/lib/_http_outgoing.js#L624)) -- and different runtimes do it slightly differently :( I think best...

Can you please share more of story (the usecase examples and why it could be a useful generic feature)

@himself65 i see it is solved (?) in https://github.com/better-auth/better-auth/pull/4113? Line you are refering to is simply for interop-default which has been enabled in latest major of jiti/c12.

PR welcome to add an option for supporting this for loading config files. There might be a case that config object has both top level keys and default and we...

@oasisniikawa nodejs compat handling with nuxt hub is different. i suggest you report it there.