Daniel Roe
Daniel Roe
Let's follow upstream issue on https://github.com/unjs/ohmyfetch/issues/37.
What are you trying to do with a dynamic import of CSS? You may be able to do what you want with: ```js if (process.client) { import("@/styles/async.scss"); } ```
Within the Vue part of your app, you can create a custom composable. ```js export const useMyApi = (url, options) => useFetch(url, { // your defaults key: url, ...options })...
A different baseURL is an example of why setting these properties on the default `$fetch` would cause problems. Nitro uses `$fetch` itself to perform fetches 'within' the server, and if...
You can track in https://github.com/vuejs/core/issues/6651.
@jgupta We _should_ already do that: https://github.com/nuxt/framework/blob/5855ba4684e36eb1e785f377d034277f008bc92a/packages/vite/src/server.ts#L132-L140 Would you provide a sandbox in which `entry.css` is render blocking?
You're right, it seems blocking, and it shouldn't be. I've raised https://github.com/nuxt-contrib/vue-bundle-renderer/pull/39 to address that issue.
Agreed. I think it is best to completely remove support for inlining entry CSS for now. ~> https://github.com/nuxt/framework/pull/8666
This will be in rc13.
This sounds good to me 👍