\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",[2027,2028],{"name":2014,"color":2015},{"name":2029,"color":2030},"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.697045,{"description":2039,"labels":2040,"number":2031,"owner":1985,"repository":2042,"state":2033,"title":2043,"updated_at":2044,"url":2045,"score":2037},"### 🐛 The bug\n\nUsing a script composable with a custom trigger multiple times across the app can cause the following warning to appear during SSR:\n```\nMaxListenersExceededWarning: Possible EventTarget memory leak detected. 11 abort listeners added to [AbortSignal]. MaxListeners is 10. Use events.setMaxListeners() to increase limit\n```\n\nIn the reproduction I created a component which uses a meta pixel script with a consent trigger. List-rendering such a component can easily exhaust the amount of listeners that is \"available\" by default.\n\n~Deduplication of the script composable for instance via `createSharedComposable` from vueuse can temporarily work around this~ (don't do this or you lose script tags in ssr after first visit), however this will only delay the warning from appearing until more are added with a custom trigger as the app grows.\n\n### 🛠️ To reproduce\n\nhttps://stackblitz.com/edit/nuxt-starter-coxfcz\n\n### 🌈 Expected behavior\n\n🌈 \n\n### ℹ️ Additional context\n\nThe actual source where the event listener is added is in unhead (visible when `--trace-warnings` is enabled): https://github.com/unjs/unhead/blob/ad0c1bfba45ceca017058016182c910cfee220f8/packages/unhead/src/composables/useScript.ts#L158",[2041],{"name":2014,"color":2015},"scripts","Having too many script composables triggers MaxListenersExceededWarning on server side","2024-10-14T05:11:14Z","https://github.com/nuxt/scripts/issues/291",{"description":2047,"labels":2048,"number":2055,"owner":1985,"repository":2056,"state":2033,"title":2057,"updated_at":2058,"url":2059,"score":2060},"Blocked by #685",[2049,2052],{"name":2050,"color":2051},"enhancement","1ad6ff",{"name":2053,"color":2054},"responsive","1cd1c6",686,"nuxt.com","[Modules] Experiment removing the hero on mobile","2023-10-10T14:45:22Z","https://github.com/nuxt/nuxt.com/issues/686",0.7149152,{"description":2062,"labels":2063,"number":2055,"owner":1985,"repository":2066,"state":2033,"title":2067,"updated_at":2068,"url":2069,"score":2060},"### Environment\n\n```\r\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v18.16.1\r\n- Nuxt Version: 3.8.2\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: yarn@3.6.0\r\n- Builder: -\r\n- User Config: app, css, build, devServer, modules, runtimeConfig, nitro, vite, i18n, hooks\r\n- Runtime Modules: @nuxtjs/tailwindcss@6.10.1, @pinia/nuxt@0.4.11, @pinia-plugin-persistedstate/nuxt@1.2.0, @thrivadev/thrive/nuxt@2.1.1, @vueuse/nuxt@10.7.0, @nuxtjs/i18n@8.0.0-rc.9, @vee-validate/nuxt@4.12.2\r\n- Build Modules: -\r\n------------------------------\r\n```\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-tqbkqz\n\n### Describe the bug\n\nThe mocked `RouterLink` [component](https://github.com/nuxt/test-utils/blob/main/src/runtime-utils/components/RouterLink.ts) is passing `props.to` directly as the href, however this results in the href being an object when `to` is an object (e.g. if passing through `path` and `state`).\r\n\r\nThis causes tests to fail even though the links work fine in the browser\r\n\r\n```\r\n- http://localhost:3000/thelink\r\n+ http://localhost:3000/[object%20Object]\r\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2064,2065],{"name":2014,"color":2015},{"name":2029,"color":2030},"test-utils","RouterLink not using correct href","2024-01-05T07:40:29Z","https://github.com/nuxt/test-utils/issues/686",{"description":2071,"labels":2072,"number":2082,"owner":1985,"repository":1985,"state":2033,"title":2083,"updated_at":2084,"url":2085,"score":2086},"### 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_",[2073,2074,2077,2080,2081],{"name":2011,"color":2012},{"name":2075,"color":2076},"3.x","29bc7f",{"name":2078,"color":2079},"dx","C39D69",{"name":2014,"color":2015},{"name":2017,"color":2018},21684,"Can't import types like `Ref` from `#imports`","2023-06-26T15:53:31Z","https://github.com/nuxt/nuxt/issues/21684",0.7223968,{"description":2088,"labels":2089,"number":2093,"owner":1985,"repository":1985,"state":2033,"title":2094,"updated_at":2095,"url":2096,"score":2097},"### Environment\n\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v20.11.0\r\n- Nuxt Version: 3.12.4\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: pnpm@9.3.0\r\n- Builder: -\r\n- User Config: compatibilityDate, devtools, devServer, modules, primevue, sourcemap, nitro, robots, sitemap, schemaOrg\r\n- Runtime Modules: @primevue/nuxt-module@4.0.4, @nuxtjs/seo@2.0.0-rc.18\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nFirst, I ran the command `npx nuxi@latest module add seo ` to add the SEO module to my Nuxt project. Then, I encountered an issue that the type hints for `defineWebSite` function are not functioning correctly.\r\n\n\n### Describe the bug\n\nhttps://github.com/unjs/unhead/blob/main/packages/schema-org/package.json\r\n\r\n```typescript\r\n //file .nuxt\\types\\imports.d.ts\r\n\r\n const defineWebPage: typeof import('../../node_modules/.pnpm/@unhead+schema-org@1.9.16/node_modules/@unhead/schema-org/vue')['defineWebPage']\r\n const defineWebSite: typeof import('../../node_modules/.pnpm/@unhead+schema-org@1.9.16/node_modules/@unhead/schema-org/vue')['defineWebSite']\r\n```\r\n\r\nBecause `./vue` is a `Subpath Export` rather than a real path, the import function cannot correctly import it.\r\n\r\n\r\nIf it were changed to the following, the type hints would work correctly.\r\n```typescript\r\n const defineWebPage: typeof import('../../node_modules/.pnpm/@unhead+schema- org@1.9.16/node_modules/@unhead/schema-org/dist/vue')['defineWebPage']\r\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2090],{"name":2091,"color":2092},"pending triage","E99695",28622,"third-party module type hints error","2024-09-07T17:10:53Z","https://github.com/nuxt/nuxt/issues/28622",0.7237608,{"description":2099,"labels":2100,"number":2108,"owner":1985,"repository":1985,"state":2033,"title":2109,"updated_at":2110,"url":2111,"score":2112},"### Environment\n\nNuxi 3.5.0 15:06:23\r\n 15:06:24\r\nRootDir: E:/workspace/GuYi_production/display-shop-new-version 15:06:24 \r\nNuxt project info: 15:06:24\r\n\r\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v18.14.2\r\n- Nuxt Version: 3.5.0\r\n- Nitro Version: 2.4.1\r\n- Package Manager: npm@9.5.0\r\n- Builder: vite\r\n- User Config: imports, app, css, vite, typescript\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n👉 Report an issue: https://github.com/nuxt/nuxt/issues/new 15:06:24 \r\n\r\n👉 Suggest an improvement: https://github.com/nuxt/nuxt/discussions/new\r\n\r\n👉 Read documentation: https://nuxt.com\n\n### Reproduction\n\nLocal operation without connection\n\n### Describe the bug\n\nAfter upgrading from version 3.3 to version 3.5 npm install\r\nrun dev\r\n\r\n\r\nI tried 3.4.3 again, everything is normal\r\nI opened the configuration file again and found that all types reported errors, which did not appear in previous versions\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n1、\r\n(property) autoImport: boolean\r\nArgument of type '{ imports: { autoImport: boolean; }; app: { head: { title: string; meta: ({ charset: string; } | { name: string; content: string; } | { hid: string; name: string; content: string; })[]; link: { rel: string; type: string; href: string; }[]; noscript: { ...; }[]; }; }; css: string[]; vite: { ...; }; typescript: { ...;...' is not assignable to parameter of type 'InputConfig\u003CNuxtConfig, ConfigLayerMeta>'.\r\n Object literal may only specify known properties, and 'imports' does not exist in type 'InputConfig\u003CNuxtConfig, ConfigLayerMeta>'.ts(2345)\r\n2、\r\n[worker reload] [worker init] Named export 'stringify' not found. The requested module 'file://E:/workspace/GuYi_production/display-shop-new-version/node_modules/devalue/dist/devalue.umd.js' is a CommonJS module, which may not support all module.exports as named exports.\r\nCommonJS modules can always be imported via the default export, for example using:\r\n 14:59:38 \r\nimport pkg from 'file://E:/workspace/GuYi_production/display-shop-new-version/node_modules/devalue/dist/devalue.umd.js'; \r\nconst { stringify, uneval } = pkg;\r\n\r\n import { stringify, uneval } from 'E:/workspace/GuYi_production/display-shop-new-version/node_modules/devalue/dist/devalue.umd.js';\r\n ^^^^^^^^^\r\n SyntaxError: Named export 'stringify' not found. The requested module 'E:/workspace/GuYi_production/display-shop-new-version/node_modules/devalue/dist/devalue.umd.js' is a CommonJS module, which may not support all module.exports as named exports. \r\n CommonJS modules can always be imported via the default export, for example using:\r\n\r\n import pkg from 'E:/workspace/GuYi_production/display-shop-new-version/node_modules/devalue/dist/devalue.umd.js';\r\n const { stringify, uneval } = pkg;\r\n\r\n at ModuleJob._instantiate (node:internal/modules/esm/module_job:124:21) at async ModuleJob.run (node:internal/modules/esm/module_job:190:5)\n```\n",[2101,2102,2103,2106],{"name":2075,"color":2076},{"name":2091,"color":2092},{"name":2104,"color":2105},"upstream","E8A36D",{"name":2107,"color":2018},"needs reproduction",20906,"after update 3.3.2 to 3.5.0 run dev Named export 'stringify' not found at ModuleJob._instantiate","2024-03-08T09:19:00Z","https://github.com/nuxt/nuxt/issues/20906",0.7246356,["Reactive",2114],{},["Set"],["ShallowReactive",2117],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"BMFTkansjFX9zbTVlMAqFLNJlkvYBUdV8ptaA-SgEP8":-1},"/nuxt/nuxt.com/1135"]