\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",[2039,2042],{"name":2040,"color":2041},"bug","d73a4a",{"name":2043,"color":2044},"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.6673477,{"description":2053,"labels":2054,"number":2045,"owner":1991,"repository":2056,"state":2047,"title":2057,"updated_at":2058,"url":2059,"score":2051},"### 🐛 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",[2055],{"name":2040,"color":2041},"scripts","Having too many script composables triggers MaxListenersExceededWarning on server side","2024-10-14T05:11:14Z","https://github.com/nuxt/scripts/issues/291",{"description":2061,"labels":2062,"number":2066,"owner":1991,"repository":1992,"state":2047,"title":2067,"updated_at":2068,"url":2069,"score":2070},"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 !",[2063],{"name":2064,"color":2065},"marketing","f5c828",1135,"[Partner page] Create Macopedia partner page","2023-06-06T12:14:39Z","https://github.com/nuxt/nuxt.com/issues/1135",0.68808645,{"labels":2072,"number":2080,"owner":1991,"repository":1991,"state":2047,"title":2081,"updated_at":2082,"url":2083,"score":2084},[2073,2076,2077],{"name":2074,"color":2075},"3.x","29bc7f",{"name":2040,"color":2041},{"name":2078,"color":2079},"🔨 p3-minor","FBCA04",14242,"ref is not defined when import.meta.glob is used when template has an html class","2023-01-19T17:30:08Z","https://github.com/nuxt/nuxt/issues/14242",0.70508945,{"description":2086,"labels":2087,"number":2088,"owner":1991,"repository":1992,"state":2047,"title":2089,"updated_at":2090,"url":2091,"score":2092},"[Pretty sure this is where a \"rounded-xl\" belongs](https://github.com/nuxt/nuxt.com/blob/b95197b97fc1acbe3582f95589856e9c97fef703/components/home/HomeSectionFeatures.vue#L22), I don't use Vue nor Nuxt so I have no idea how to navigate the codebase & I don't want to make a PR which is potentially incapable of building (too lazy to set up and test change)\n\nWhat it should look like:\n\n\nWhat it actually looks like:\n\n\nAdding a \"rounded-xl\" tailwind class to the sub-div (selected in this screenshot) fixes this and makes it look (presumably) as intended ([as the first screenshot shows](https://github.com/user-attachments/assets/731610cf-9cf9-464f-bf6f-0daff32e8fc4))\n\n",[],1679,"Presumably unintentional dark edges on corners of card","2024-10-13T10:45:20Z","https://github.com/nuxt/nuxt.com/issues/1679",0.71183074,{"description":2094,"labels":2095,"number":2099,"owner":1991,"repository":2007,"state":2047,"title":2100,"updated_at":2101,"url":2102,"score":2103},"I have a custom composable (`useConsent`), which I am trying to mock. \r\nI'm importing the composable like so:\r\n\r\n`import { useConsent, useHead } from '#imports'`.\r\n\r\nThe import is recognized in `packages/vitest-environment-nuxt/src/modules/mock.ts`:\r\n```\r\n{\r\n name: \"default\",\r\n as: \"useConsent\",\r\n from: \"[...]/src/runtime/composables/useConsent.ts\",\r\n priority: undefined,\r\n}\r\n```\r\n\r\nEven though the import is recognized and no `\"Cannot find import to mock\"` error is thrown, the import is not mocked.\r\nIn the same file I am mocking `useHead`, that one is mocked without any issues.\r\n\r\nUsing `nuxt-vitest@0.8.4`\r\n",[2096],{"name":2097,"color":2098},"vitest-environment","b60205",524,"custom composable without function name not mocked with `mockNuxtImport`","2023-12-02T00:17:13Z","https://github.com/nuxt/test-utils/issues/524",0.7137082,["Reactive",2105],{},["Set"],["ShallowReactive",2108],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"x5RHh7yS0UywnySiQ6mEfuOWnCM6mm8FSAOeCMDdEJY":-1},"/nuxt/icon/358"]