Daniel Roe
Daniel Roe
oh dear - thanks for letting me know 😆
I think we experienced this also in https://github.com/nuxt-modules/tailwindcss - reverted in https://github.com/nuxt-modules/tailwindcss/pull/867.
i see merit in that. perhaps `: false`? we already support this syntax for certain modules, like telemetry or devtools.
I could see no reproduction link in that issue
It's possible that nuxt/fonts might process something that _isn't_ a valid font (and therefore can't resolve it). So I think the scenarios we should care about are: - if the...
It might fail - I think - if the font family isn't a web font or if it's processing a css variable which doesn't have a font family.
we can use https://github.com/unjs/unifont/pull/161 once the next release of unifont
This is because we explicitly check for imports so we don't inject keys into similarly named but different composables. https://github.com/nuxt/nuxt/blob/860cfe16b3e2bda4e4e3e02a66d37921cbca406d/packages/vite/src/plugins/composable-keys.ts#L56-L76
yes that's a good solution we could also look at removing that restriction
you could dynamically set the loading template function by configuring the schema here using a `$resolve` function: https://github.com/nuxt/nuxt/blob/64287dbd5c150775c1fe94a6d6dcd8ec7e805e40/packages/schema/src/config/dev.ts#L37-L42