Pooya Parsa
Pooya Parsa
@gioboa routeRules: { "**": {} } you can add it to test fixture (or change an existing one and remove leading /)
I guess because it is empty object not being effective. You might need to add something to it like `{ headers: { "x-foo": "bar" } }`. This issue is more...
Do you call `runtimeConfig(event)` inside an event handler? Due to how late cloudflare provides environment (during request) it is a limitation.
please provide a minimal reproduction 🙏🏼
I think the easiest way is to explicitly add `routeRules` entries for asset path cache headers. (nitro cannot safely assume to apply headers to paths that can fallback to other...
I am experiencing similar issue with latest vitest (v4) on deno: https://github.com/h3js/srvx/pull/138 (reported to https://github.com/vitest-dev/vitest/issues/8896)
reopening issue to try to make nitro plugin behavior smarter when running within tests.
@theoludwig yes it is a good workaround. i am investigating first-class vitest support, nitro already can setup a good vitest runner enviornment small changes needed.
/cc @juliusmarminge. You should disable plugin for test environment. Probably best we do it out of the box until vitest support lands.
Another alternative: https://github.com/unjs/uqr