\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",[2016,2019],{"name":2017,"color":2018},"bug","d73a4a",{"name":2020,"color":2021},"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.4498134,{"description":2030,"labels":2031,"number":2037,"owner":1985,"repository":1985,"state":2024,"title":2038,"updated_at":2039,"url":2040,"score":2041},"### 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_",[2032,2035],{"name":2033,"color":2034},"3.x","29bc7f",{"name":1996,"color":2036},"E99695",24653,"can't use type Ref without getting error","2023-12-13T09:14:53Z","https://github.com/nuxt/nuxt/issues/24653",0.6892718,{"description":2043,"labels":2044,"number":2048,"owner":1985,"repository":2049,"state":2024,"title":2050,"updated_at":2051,"url":2052,"score":2053},"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 !",[2045],{"name":2046,"color":2047},"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.69156444,{"description":2055,"labels":2056,"number":2059,"owner":1985,"repository":1999,"state":2024,"title":2060,"updated_at":2061,"url":2062,"score":2063},"### Environment\n\n```\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v20.14.0\r\n- Nuxt Version: 3.12.2\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.6\r\n- Package Manager: npm@10.7.0\r\n- Builder: -\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n```\n\n### Reproduction\n\nCall `createPage()` by passing `javaScriptEnabled: false` in the options:\r\n\r\n```typescript\r\nconst page = await createPage('/foobar', {\r\n javaScriptEnabled: false,\r\n })\r\n```\n\n### Describe the bug\n\nThis will never finish loading the page because the `createPage` method always waits for hydration to finish. In this case, hydration can't ever finish, so the method's Promise never resolves.\n\n### Additional context\n\nProbably a rare use case, but I ran into this issue while explicitly wanting to test the unhydrated SSR output of a page.\n\n### Logs\n\n_No response_",[2057,2058],{"name":2017,"color":2018},{"name":2020,"color":2021},868,"Setting `javaScriptEnabled: false` in `createPage()` never loads page","2024-12-04T16:34:32Z","https://github.com/nuxt/test-utils/issues/868",0.6920651,{"description":2065,"labels":2066,"number":2074,"owner":1985,"repository":1985,"state":2024,"title":2075,"updated_at":2076,"url":2077,"score":2078},"### 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_",[2067,2070,2071],{"name":2068,"color":2069},"discussion","538de2",{"name":2033,"color":2034},{"name":2072,"color":2073},"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.6942062,{"description":2080,"labels":2081,"number":2093,"owner":1985,"repository":1985,"state":2024,"title":2094,"updated_at":2095,"url":2096,"score":2097},"### 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_",[2082,2085,2086,2089,2090],{"name":2083,"color":2084},"types","2875C3",{"name":2033,"color":2034},{"name":2087,"color":2088},"dx","C39D69",{"name":2017,"color":2018},{"name":2091,"color":2092},"🔨 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.69439,{"description":2099,"labels":2100,"number":1998,"owner":1985,"repository":2049,"state":2024,"title":2103,"updated_at":2104,"url":2105,"score":2003},"\n\n",[2101],{"name":2017,"color":2102},"ff281a","[Home] Responsive hero","2023-02-15T12:30:55Z","https://github.com/nuxt/nuxt.com/issues/750",["Reactive",2107],{},["Set"],["ShallowReactive",2110],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"4bg1PIOltNihnOclnrq9O08Sw52tOCOVR4mGrrRbqJE":-1},"/nuxt/scripts/291"]