Daniel Roe

that would be a nice idea! I'd like to see them stabilised first (so the API wouldn't change - cc: @pi0) and yes, being able to run tasks on build/deploy...

This would definitely be a nice feature. You'll get the benefit of this if you statically generate your site. You (should) also be able to turn on `experimental.payloadExtraction` even if...

When using a custom fetch, Nuxt does not perform 'internal' fetches or pass on headers automatically - you will need to do this manually if that's the behaviour you want.

@MickL We will not support setting baseURL globally for `useFetch` and `$fetch`, because it would break the 'internal' fetches on the server, as well as any modules or internal Nuxt...

The issue here is coming from `pinia` and will be resolved in v3 of `pinia`.

we might need a hook for nitro like `prepare:types` for nuxt that lets us modify the generated file also, I'm thinking of moving to this pattern for the tsconfig: https://github.com/danielroe/roe.dev/blob/main/tsconfig.json...

I was thinking to rename to `nuxt/eslint` and include plugin in this repo.

I'm thinking: ```ts export default defineNuxtConfig({ runtimeConfig: { // should be process.env.NUXT_GITHUB_TOKEN githubToken: process.env.MY_GITHUB_TOKEN, public: { // should be process.env.NUXT_PUBLIC_SOME_VAR someVar: process.env.SOMEVAR } } }) ``` The reason being that...

yes, it might be worth retrying the fetch a couple of times, and if not - failing the build ... we can implement in https://github.com/unjs/unifont.

✅ Done - latest release should pull in the latest `unifont` changes.