\r\n \u003Cp>This is a test\u003C/p>\r\n \u003C/div>\r\n\u003C/template>\r\n\u003Cstyle>\r\np {\r\n font: 1.25rem/1.75rem Lato, serif;\r\n/* font-family: Lato, serif; */\r\n}\r\n\u003C/style>\r\n```\r\n\r\nIt seems to me that toggling betwen \"font:\" and \"font-family:\" in the css makes Lato (or any other font) appear or disappear in the devtools fonts tab. \r\n\r\nOf course, it's also possible that I might be doing something very stupid. Or that the fonts module does not respect \"fonts:\" by design.\r\n\r\nSometimes \"npm run dev\" is required to show this behaviour.\r\n\r\nExamples:\r\n\r\n\r\n\r\n\r\n",[2914,2917],{"name":2915,"color":2916},"bug","d73a4a",{"name":2918,"color":2919},"good first issue","7057ff",291,"fonts","closed","support scanning font families from \"font:\"","2024-10-01T15:09:50Z","https://github.com/nuxt/fonts/issues/291",0.46636504,{"description":2928,"labels":2929,"number":2935,"owner":2868,"repository":2868,"state":2922,"title":2936,"updated_at":2937,"url":2938,"score":2939},"### Environment\n\n- Operating System: Windows_NT\r\n- Node Version: v18.19.0\r\n- Nuxt Version: 3.8.0\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: css, extends, typescript, runtimeConfig, modules, directus\r\n- Runtime Modules: nuxt-directus@5.6.0\r\n- Build Modules: -\n\n### Reproduction\n\n`import { Ref } from 'vue';`\r\n`const testVar: Ref\u003Cany> = ref(null)`\n\n### Describe the bug\n\nHere is the error I get :\r\n`The requested module '/_nuxt/node_modules/.cache/vite/client/deps/vue.js?v=b0c30841' does not provide an export named 'Ref'`\r\nwhen I want to type my vars in vue components\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2930,2933],{"name":2931,"color":2932},"3.x","29bc7f",{"name":2879,"color":2934},"E99695",24653,"can't use type Ref without getting error","2023-12-13T09:14:53Z","https://github.com/nuxt/nuxt/issues/24653",0.68727165,{"description":2941,"labels":2942,"number":2954,"owner":2868,"repository":2868,"state":2922,"title":2955,"updated_at":2956,"url":2957,"score":2958},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.15.0`\r\n- Nuxt Version: `3.5.3`\r\n- Nitro Version: `2.5.0`\r\n- Package Manager: `pnpm@8.6.2`\r\n- Builder: `vite`\r\n- User Config: `devtools`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\nThis will result in an error because the type `Ref` is not found in `#imports`.\r\n```js\r\nimport { ref, type Ref } from '#imports'\r\n```\r\n\r\nor is this the correct approach..? (by the way I have set `autoImport: false` in `nuxt.config.ts`)\r\nActually, importing from 'vue' seems clearer to me than importing from '#imports'.\r\n```js\r\nimport { ref, type Ref } from 'vue'\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2943,2946,2947,2950,2951],{"name":2944,"color":2945},"types","2875C3",{"name":2931,"color":2932},{"name":2948,"color":2949},"dx","C39D69",{"name":2915,"color":2916},{"name":2952,"color":2953},"🔨 p3-minor","FBCA04",21684,"Can't import types like `Ref` from `#imports`","2023-06-26T15:53:31Z","https://github.com/nuxt/nuxt/issues/21684",0.6992003,{"description":2960,"labels":2961,"number":2965,"owner":2868,"repository":2966,"state":2922,"title":2967,"updated_at":2968,"url":2969,"score":2970},"All information are [on the form](https://docs.google.com/forms/d/1wj_8SJSKsBbAl2LHP_FXN1hmX2F9q0exgnMgnqItOew/edit#response=ACYDBNiEAjSFS14oLMASHl7Bakxyba9MzTsV9gUM3-EFLRaQ9PcQISs5YXoEXTo2zojHPxo)\n\nAnd the logos are in your mailbox !",[2962],{"name":2963,"color":2964},"marketing","f5c828",1135,"nuxt.com","[Partner page] Create Macopedia partner page","2023-06-06T12:14:39Z","https://github.com/nuxt/nuxt.com/issues/1135",0.6999684,{"description":2972,"labels":2973,"number":2981,"owner":2868,"repository":2868,"state":2922,"title":2982,"updated_at":2983,"url":2984,"score":2985},"### Environment\n\n------------------------------\r\n- Operating System: `Darwin`\r\n- Node Version: `v16.16.0`\r\n- Nuxt Version: `3.0.0-rc.9`\r\n- Nitro Version: `0.5.0`\r\n- Package Manager: `pnpm@7.11.0`\r\n- Builder: `vite`\r\n- User Config: `typescript`, `css`, `components`, `modules`, `runtimeConfig`, `vglStore`\r\n- Runtime Modules: `~/nuxt-modules/routes-module.ts`, `@pinia/nuxt`, `@vueuse/nuxt@9.2.0`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-cyy9sn?file=app.vue\n\n### Describe the bug\n\nI'm constantly forgetting to add `.value` when working with refs and wondered why eslint is not helping me – no visual hints in VS Code and no error when running eslint in terminal.\r\nThere is a rule from `eslint-plugin-vue` to catch this: [vue/no-ref-as-operand](https://eslint.vuejs.org/rules/no-ref-as-operand.html)\r\nTurns out, the auto imported `ref` from `#imports` is somehow \"different\" than directly importing from `vue`.\r\nIf I do `import { ref } from 'vue'`, I get squiggly lines in VS Code and `.value` is automatically added when I save the file.\r\nSee also simple reproduction above.\r\n\r\n```vue\r\n\u003Cscript setup lang=\"ts\">\r\n// uncomment this will throw vue/no-ref-as-operand\r\n// import { ref } from 'vue';\r\n\r\n// uncomment this will not help\r\n// import { ref } from '#imports';\r\n\r\nconst count = ref(1);\r\n\r\n// NOTE: should be count.value\r\nconst foo = count + 1;\r\n\r\nconsole.log(foo);\r\n\u003C/script>\r\n```\r\n\r\nNot sure if this should be fixed in `eslint-plugin-vue` or here.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2974,2977,2978],{"name":2975,"color":2976},"discussion","538de2",{"name":2931,"color":2932},{"name":2979,"color":2980},"upstream","E8A36D",14882,"auto imported `ref` will not trigger `vue/no-ref-as-operand` warning from eslint-plugin-vue","2024-04-09T08:17:09Z","https://github.com/nuxt/nuxt/issues/14882",0.7013165,{"description":2987,"labels":2988,"number":158,"owner":2868,"repository":2882,"state":2922,"title":2989,"updated_at":2990,"url":2991,"score":2992},"It seems that v0.2.2 is the latest available release according to npm and Github. However there have been 18 commits to `main` since then. Is this a deliberate choice **not** to release or some automation that has stopped working?\r\nhttps://github.com/nuxt/test-utils/compare/v0.2.2...main\r\n\r\n~As an aside I am getting 500 errors from the nuxt server which is why I am digging further into things.~ Removed to keep the Issue focused ❤️ ",[],"Stale releases","2023-12-02T00:13:13Z","https://github.com/nuxt/test-utils/issues/485",0.7027317,["Reactive",2994],{},["Set"],["ShallowReactive",2997],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f4bg1PIOltNihnOclnrq9O08Sw52tOCOVR4mGrrRbqJE":-1},"/nuxt/scripts/291"]