\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",[3031,3034],{"name":3032,"color":3033},"bug","d73a4a",{"name":3035,"color":3036},"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.6983209,{"description":3045,"labels":3046,"number":3037,"owner":3021,"repository":3048,"state":3039,"title":3049,"updated_at":3050,"url":3051,"score":3043},"### 🐛 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",[3047],{"name":3032,"color":3033},"scripts","Having too many script composables triggers MaxListenersExceededWarning on server side","2024-10-14T05:11:14Z","https://github.com/nuxt/scripts/issues/291",{"description":3053,"labels":3054,"number":3061,"owner":3021,"repository":3062,"state":3039,"title":3063,"updated_at":3064,"url":3065,"score":3066},"Blocked by #685",[3055,3058],{"name":3056,"color":3057},"enhancement","1ad6ff",{"name":3059,"color":3060},"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.72051483,{"description":3068,"labels":3069,"number":3061,"owner":3021,"repository":3072,"state":3039,"title":3073,"updated_at":3074,"url":3075,"score":3066},"### 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_",[3070,3071],{"name":3032,"color":3033},{"name":3035,"color":3036},"test-utils","RouterLink not using correct href","2024-01-05T07:40:29Z","https://github.com/nuxt/test-utils/issues/686",{"description":3077,"labels":3078,"number":3079,"owner":3021,"repository":3022,"state":3039,"title":3080,"updated_at":3081,"url":3082,"score":3083},"Hi there and thanks so much for your work!\r\n\r\nRecently I've upgraded `nuxt 3.12.4` to `nuxt 3.13.2`, `@nuxt/ui@2.18.4` to `@nuxt/ui@2.18.6`, `@tailwindcss/forms@0.5.7, @tailwindcss/typography@0.5.14` to `@tailwindcss/forms@0.5.9, @tailwindcss/typography@0.5.15`. Here are some observations.\r\n\r\nIcons stop working on initial site loading (and 50/50% on next loads):\r\n\r\n1. Navigate to webpage (generated by `npm run generate`, incognito mode, no cache): no icons.\r\n2. Refresh page: sometimes there are icons, sometimes not, sometimes only half of them.\r\n\r\n```\r\nThe above happens whether one upgrades to `@nuxt/ui@2.18.6`,`@tailwindcss/forms@0.5.9, @tailwindcss/typography@0.5.15` within `nuxt 3.12.4`.\r\n\r\nOr\r\n\r\nOne upgrades to `nuxt 3.13.2` and `@nuxt/ui@2.18.6`.\r\n\r\nOr \r\n\r\nSometimes when one simply upgrades to `nuxt 3.13.2`.\r\n```\r\n\r\nWhat fixes an issue:\r\n\r\n1. Downgrading to `nuxt 3.12.4` with `@nuxt/ui@2.18.4` and `@tailwindcss/forms@0.5.7 @tailwindcss/typography@0.5.14` fixes an issue.\r\n3. Installiing collections locally (in my case `@iconify-json/bxl, @iconify-json/heroicons, @iconify-json/heroicons-solid`) and adding:\r\n```ruby\r\nicon: {\r\nclientBundle: {\r\n scan: true,\r\n sizeLimitKb: 256, }, },\r\n```\r\n\r\nHowewer one question still bothers me. Same `nuxt/ui`. `3.12.4` without the above settings works like a charm, but when updating the above deps barely loads icons. Just changing deps and the necessity of the the above arises. But why?\r\n\r\n`3.12.4` and `nuxt/ui@2.18.6` with `@tailwindcss/forms@0.5.9, @tailwindcss/typography@0.5.15` together result in the issue without the above settings (with `nuxt/ui@2.18.4` and `@tailwindcss/forms@0.5.7, @tailwindcss/typography@0.5.14` everything works fine).\r\n\r\n`3.13.2` with `nuxt/ui@2.18.6` result in the issue as well (keeping tailwind deps old). And sometimes just upgrading to `3.13.2` results in the issue.\r\n\r\nWith the minimal amount of site payload (one page - 2-3 icons) - `3.13.2` works fine without the above changes. When full project is in place - icons without the above changes stop working. I'm talking about `npm run generate` with `ssr:true`. `npm run build` works in every case.\r\n\r\nCan someone elaborate?\r\n\r\nAlso you can easily reproduce this behavior (node `v20.17.0)`. \r\n1. repo: https://github.com/gAlleb/nuxt-om\r\n2. `npm install`.\r\n3. Run `npm run generate` - all icons work fine.\r\n\r\n4. Upgrade `npm install @nuxt/ui@2.18.6 @tailwindcss/forms@0.5.9 @tailwindcss/typography@0.5.15`.\r\n\r\nor\r\n\r\n5. Upgrade `npx nuxi upgrade` and `npm install @nuxt/ui@2.18.6`\r\n\r\n6. Navigate to webpage (generated by `npm run generate`, incognito mode, no cache).\r\n\r\n7. Icons won't load without `clientBundle` setting and adding `local collections`.\r\n\r\nThanks!\r\n\r\n\r\n\r\n\r\n\r\n",[],259,"Icons aren't loaded (@nuxt-ui)","2024-11-20T16:54:06Z","https://github.com/nuxt/icon/issues/259",0.7211868,{"description":3085,"labels":3086,"number":3093,"owner":3021,"repository":3021,"state":3039,"title":3094,"updated_at":3095,"url":3096,"score":3097},"### 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_",[3087,3090],{"name":3088,"color":3089},"3.x","29bc7f",{"name":3091,"color":3092},"pending triage","E99695",24653,"can't use type Ref without getting error","2023-12-13T09:14:53Z","https://github.com/nuxt/nuxt/issues/24653",0.7243478,{"description":3099,"labels":3100,"number":3105,"owner":3021,"repository":3021,"state":3039,"title":3106,"updated_at":3107,"url":3108,"score":3109},"### Environment\n\nN/A\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-pqgjqen4?file=demo.mjs\n\n### Describe the bug\n\nCode that utilizes [named imports/exports](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import#named_import) that have the string syntax to declare arbitrary (non js identifier) names, fail to build with nuxt 3.16.0 (dev mode works). Build works when downgrading back to 3.15.4.\n\n```js\nconst a = 10\n\nexport { a as 'name.with.dots' }\n```\n\n```vue\n\u003Ctemplate>\n \u003Cdiv>\n \u003CNuxtRouteAnnouncer />\n \u003CNuxtWelcome />\n \u003C/div>\n\u003C/template>\n\n\u003Cscript lang=\"js\">\nimport * as demo from './demo.mjs'\n\nconsole.log(demo['name.with.dots'])\n\u003C/script>\n\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n> build\n> nuxt build\n\nNuxt 3.16.0 with Nitro 2.11.5 nuxi 18:04:46\nℹ Building for Nitro preset: node-server nuxi 18:04:46\nℹ Building client... 18:04:47\nℹ vite v6.2.1 building for production... 18:04:47\nℹ ✓ 128 modules transformed. 18:04:48\nℹ .nuxt/dist/client/manifest.json 1.06 kB │ gzip: 0.29 kB 18:04:48\nℹ .nuxt/dist/client/_nuxt/error-500.dGVH929u.css 1.88 kB │ gzip: 0.72 kB 18:04:48\nℹ .nuxt/dist/client/_nuxt/error-404.C3V-3Mc4.css 3.56 kB │ gzip: 1.10 kB 18:04:48\nℹ .nuxt/dist/client/_nuxt/entry.ofCu9KLV.css 12.41 kB │ gzip: 2.57 kB 18:04:48\nℹ .nuxt/dist/client/_nuxt/z7DXRpCd.js 3.39 kB │ gzip: 1.53 kB 18:04:48\nℹ .nuxt/dist/client/_nuxt/DUuvXmrT.js 9.42 kB │ gzip: 3.76 kB 18:04:48\nℹ .nuxt/dist/client/_nuxt/y94aZ4V3.js 220.05 kB │ gzip: 63.21 kB 18:04:48\nℹ ✓ built in 906ms 18:04:48\n✔ Client built in 921ms 18:04:48\nℹ Building server... 18:04:48\nℹ vite v6.2.1 building SSR bundle for production... 18:04:48\nℹ ✓ 53 modules transformed. 18:04:48\n\n ERROR ✗ Build failed in 350ms 18:04:48\n\n\n ERROR Nuxt Build Error: [vite:esbuild-transpile] Transform failed with 1 error: nuxi 18:04:48\ndemo.mjs:3:14: ERROR: Using the string \"name.with.dots\" as an export name is not supported in the configured target environment (\"chrome87\", \"edge88\", \"es2020\", \"firefox78\", \"safari14\" + 2 overrides)\nfile: demo.mjs:3:14\n\nUsing the string \"name.with.dots\" as an export name is not supported in the configured target environment (\"chrome87\", \"edge88\", \"es2020\", \"firefox78\", \"safari14\" + 2 overrides)\n1 | const a = 10;\n2 |\n3 | export { a as \"name.with.dots\" };\n | ^\n\n\n demo.mjs:3:14: ERROR: Using the string \"name.with.dots\" as an export name is not supported in the configured target environment (\"chrome87\", \"edge88\", \"es2020\", \"firefox78\", \"safari14\" + 2 overrides)\n file: demo.mjs:3:14\n\n Using the string \"name.with.dots\" as an export name is not supported in the configured target environment (\"chrome87\", \"edge88\", \"es2020\", \"firefox78\", \"safari14\" + 2 overrides)\n 1 | const a = 10;\n 2 |\n 3 | export { a as \"name.with.dots\" };\n | ^\n\n at failureErrorWithLog (node_modules\\esbuild\\lib\\main.js:1477:15)\n at node_modules\\esbuild\\lib\\main.js:756:50\n at responseCallbacks.\u003Ccomputed> (node_modules\\esbuild\\lib\\main.js:623:9)\n at handleIncomingPacket (node_modules\\esbuild\\lib\\main.js:678:12)\n at Socket.readFromStdout (node_modules\\esbuild\\lib\\main.js:601:7)\n at Socket.emit (node:events:524:28)\n at addChunk (node:internal/streams/readable:561:12)\n at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)\n at Readable.push (node:internal/streams/readable:392:5)\n at Pipe.onStreamRead (node:internal/stream_base_commons:189:23)\n\n```",[3101,3104],{"name":3102,"color":3103},"workaround available","11376d",{"name":3091,"color":3092},31266,"Building code dependent on named imports fails in 3.16.0","2025-04-18T11:02:36Z","https://github.com/nuxt/nuxt/issues/31266",0.7247239,{"labels":3111,"number":3120,"owner":3021,"repository":3021,"state":3039,"title":3121,"updated_at":3122,"url":3123,"score":3124},[3112,3113,3114,3117],{"name":3088,"color":3089},{"name":3032,"color":3033},{"name":3115,"color":3116},"upstream","E8A36D",{"name":3118,"color":3119},"🔨 p3-minor","FBCA04",14550,"500 _unref is not defined","2023-01-19T17:36:59Z","https://github.com/nuxt/nuxt/issues/14550",0.7252712,{"labels":3126,"number":3132,"owner":3021,"repository":3021,"state":3039,"title":3133,"updated_at":3134,"url":3135,"score":3136},[3127,3128,3129],{"name":3088,"color":3089},{"name":3032,"color":3033},{"name":3130,"color":3131},"vite","3574D1",12683,"Failed to resolve import \"#build/plugins\" when adding alias for `@vue/composition-api`","2023-01-19T16:14:51Z","https://github.com/nuxt/nuxt/issues/12683",0.7258755,["Reactive",3138],{},["Set"],["ShallowReactive",3141],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fBMFTkansjFX9zbTVlMAqFLNJlkvYBUdV8ptaA-SgEP8":-1},"/nuxt/nuxt.com/1135"]