Mick Lawitzke
Mick Lawitzke
Love it! A few suggestions, not sure if implemented: - `event.context` should have some flag that is set to true if current request is an internal fetch (e.g. to skip...
Thanks for the reply. I would still suggest: - Nitro should add a flag if a request is an internal request, e.g. `event.context.serverFetch = true` so middlewares can be skipped...
> Internal and external fetch behavior are identical I think thats a big issue. I already had this problem with Nitro v1 and it was hard to find a difference...
Another important usecase for me is to call another function (handler) e.g. when a webhook from Stripe comes in saying "product sold". Now I want to call my product-update-handler `PATCH...
I wrote it already in some Nuxt issues but I would love auto imports being fully disabled by default + all the docs updated for the reasons you stated. Personally...
Hoping to see auto imports disabled in v3 :)
Why not make auto-imports opt-out for Nuxt 4, but always set the opt-out option for new projects created with Nuxi, then disable them with Nuxt 5 but keep it opt-in?
I guess that depends on what library is used to parse the env file, some do parse to string, number, boolean, array. Btw. I dont think the Node docs are...
True! Only downside is it creates duplicate code in the final bundle. Not much but depends on how many formats and languages. Also the compiler complains, in your example that...
May I ask what the status of v3 is? :) I see the last commit is from june. Our team is considering to use Nitro for a huge project.