Pooya Parsa

Thanks for the updates specially making it opt-in @danielroe 💯 Changes look good to me overall.

@danielroe I think we should start thinking of semver/patch release branches this way we have more time for edge testing not blocked by patches :)

No i need to test the default behavior via edge channel on main branch :) Patch shouldn't be blocker will continue this on discord later today.

Disabled flag for now to land into edge/patch without being blocked. Checking (more generic) non blocker edge feat testing next week 👍🏼

Thanks. This will be supported and fixed in next version of nitro (https://github.com/unjs/nitro/commit/db6e6c299f2022eac648a9de460da982cbd2061e) However please note that by adding route rule, it will be also applied to the development time...

Thanks for explaining usecase. For custom assets dir (with cache headers), you might use something like this: ```js export default defineNuxtConfig({ nitro: { publicAssets: [ { baseURL: '/assets', dir: './assets',...

Nice work! For me it even looks good to be out of experimental flag testing on edge only. One note about implementation it would be nice if the "reload" functionality...

Normally you can use `fetch` (without `$fetch.`) prefix to use native fetch universally this seems an upstream issue with ofetch.

As we are documenting the usage and there are some valid use cases, I believe we should still expose it as a `@nuxt/kit` utility. At least managing and unifying the...

I hope issue is fixed in last release. You can try nuxi upgrade —force in cast of 2.2.1 reproducing issues, please ping me with a reproduction to reopen :)