| \u003Cimg width=\"403\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/de628eac-77c1-4994-9986-bdf53b5f3dad\" /> |\n\n## Reproduction\n\n- Stackblitz: https://stackblitz.com/edit/github-yzt752qo?file=nuxt.config.ts,tailwind.config.js\n\nApparently, it's not reproducible in Stackblitz: https://github.com/nuxt/fonts/issues/438#issuecomment-2560376071\n\nHopefully, the Stackblitz is enough to demonstrate the issue, thought.",[],578,"nuxt","fonts","open","Variation Settings not applied in variable fonts","2025-03-23T01:49:12Z","https://github.com/nuxt/fonts/issues/578",0.7256123,{"description":1993,"labels":1994,"number":1998,"owner":1985,"repository":1999,"state":1987,"title":2000,"updated_at":2001,"url":2002,"score":2003},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v20.8.1`\r\n- Nuxt Version: `3.9.0`\r\n- CLI Version: `3.10.0`\r\n- Nitro Version: `2.8.1`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `-`\r\n- User Config: `devtools`, `modules`\r\n- Runtime Modules: `@nuxt/test-utils/module@3.9.0`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-gee6qy?file=app.vue\r\n\r\n### Describe the bug\r\n\r\nOnce I expose a variable called `error` within the setup, the component fails to render. \r\nSince everything works within the dev server / build, I suspect this is something within `@nuxt/test-utils`\r\n\r\nAfter renaming the `error` variable to something else, the component can be mounted within the tests again.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell-script\r\nVitest caught 1 unhandled error during the test run.\r\nThis might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.\r\n\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\nTypeError: 'set' on proxy: trap returned falsish for property 'error'\r\n ❯ clonedComponent.render node_modules/@nuxt/test-utils/dist/runtime-utils/index.mjs:128:44\r\n 126| renderContext[key] = passedProps[key];\r\n 127| }\r\n 128| return render.call(this, renderContext, ...args);\r\n | ^\r\n 129| } : void 0,\r\n 130| setup: setup ? (props2) => wrappedSetup(props2, setupContext) : void 0\r\n ❯ renderComponentRoot node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:868:16\r\n ❯ ReactiveEffect.componentUpdateFn node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:5922:46\r\n ❯ ReactiveEffect.run node_modules/@vue/reactivity/dist/reactivity.cjs.js:174:19\r\n ❯ instance.update node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:6053:16\r\n ❯ setupRenderEffect node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:6063:5\r\n ❯ eval node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:1613:9\r\n\r\nThis error originated in \"test/app.nuxt.test.ts\" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.\r\nThe latest test that might've caused the error is \"Should mount\". It might mean one of the following:\r\n- The error was thrown, while Vitest was running this test.\r\n- This was the last recorded test before the error was thrown, if error originated after test finished its execution.\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\n\r\n```\r\n```\r\n",[1995],{"name":1996,"color":1997},"bug","d73a4a",684,"test-utils","mountSuspended fails: 'set' on proxy: trap returned falsish for property 'error'","2025-03-14T15:14:45Z","https://github.com/nuxt/test-utils/issues/684",0.7680741,{"description":2005,"labels":2006,"number":2009,"owner":1985,"repository":2010,"state":2011,"title":2012,"updated_at":2013,"url":2014,"score":2015},"After updating the API, Jobs page is on error under certain circumstances : \n\nRelated commit : https://github.com/nuxtlabs/nuxt.com/commit/8962705b5d0dda99724d661efeeb4ed18e332db4\n\nEnvironment (Preview) : https://framework-p2aadzhns-nuxt-js.vercel.app/\n\n```\nTypeError: Cannot read properties of undefined (reading 'map')\n```\n\nThis is due to changes in the data structure of the API, changing from `\u003CNuxtJob[]>` to `{ data: \u003CNuxtJob[]>`. API endpoint (/api/jobs) seems to sometimes serve the outdated data.\n\n- 1 : client-side navigation from / to /support/jobs : fails\n- 2 : Server hit on /support/jobs : works\n- 3: client-side navigation back and forth to /support/jobs after 2 : works",[2007],{"name":1996,"color":2008},"ff281a",1041,"nuxt.com","closed","[Jobs] Error after API update","2023-06-06T12:14:28Z","https://github.com/nuxt/nuxt.com/issues/1041",0.7256836,{"description":2017,"labels":2018,"number":2019,"owner":1985,"repository":2010,"state":2011,"title":2020,"updated_at":2021,"url":2022,"score":2023},"Blog page:\n\n[Blog](https://nuxt.com/blog) > Release - January 30, 2023\n\nModule page:\n\n[Modules](https://nuxt.com/modules) > Security (module category)",[],1508,"Blog / Module: Improve back button to leverage breadcrumb instead","2024-02-22T15:18:14Z","https://github.com/nuxt/nuxt.com/issues/1508",0.7547675,{"description":2025,"labels":2026,"number":2033,"owner":1985,"repository":2010,"state":2011,"title":2034,"updated_at":2035,"url":2036,"score":2037},"due to the listing order being a big influence in traffic for the agency page, would it be possible for the agencies to be presented in a random order when accessing the [Agencies page](https://nuxt.com/support/agencies) ?",[2027,2030],{"name":2028,"color":2029},"enhancement","1ad6ff",{"name":2031,"color":2032},"marketing","f5c828",1048,"[Agencies] Present agencies in a random order","2023-10-10T14:45:03Z","https://github.com/nuxt/nuxt.com/issues/1048",0.75632846,{"description":2039,"labels":2040,"number":2045,"owner":1985,"repository":2046,"state":2011,"title":2047,"updated_at":2048,"url":2049,"score":2050},"### Version\n\nv3 - https://pkg.pr.new/@nuxt/ui@2e17fb6\n\n### Description\n\n* `CommandPalette` placeholder: https://github.com/nuxt/ui/blob/v3/src/runtime/components/CommandPalette.vue#L143\n",[2041,2042],{"name":1996,"color":1997},{"name":2043,"color":2044},"v3","49DCB8",2906,"ui","v3: Missing translations","2025-01-25T13:12:21Z","https://github.com/nuxt/ui/issues/2906",0.7574695,{"description":2052,"labels":2053,"number":2059,"owner":1985,"repository":2046,"state":2011,"title":2060,"updated_at":2061,"url":2062,"score":2063},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.9.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.22.3\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@8.10.2\n- Builder: -\n- User Config: devtools, vite, modules, css, compatibilityDate\n- Runtime Modules: @nuxt/ui@3.0.0-beta.2\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.15.4\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/pmvsfw\n\n### Description\n\n```\ndeclare function _useOverlay(): {\n overlays: import(\"vue\").ShallowReactive\u003COverlay[]>;\n open: \u003CT extends Component>(id: symbol, props?: ComponentProps\u003CT>) => Promise\u003Cany>;\n close: (id: symbol, value?: any) => void;\n create: \u003CT extends Component>(component: T, _options?: OverlayOptions\u003CComponentProps\u003CT>>) => OverlayInstance\u003CT>;\n patch: \u003CT extends Component>(id: symbol, props: Partial\u003CComponentProps\u003CT>>) => void;\n unMount: (id: symbol) => void;\n};\n```\ne.g:\n```\nconst overlay = useOverlay()\noverlay.create(UModal, { props: {untyped} })\n```\n\nI didn't get the correct props type when using useOverlay, and there are no property hints when passing overlay.open or the open function after create\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2054,2055,2056],{"name":1996,"color":1997},{"name":2043,"color":2044},{"name":2057,"color":2058},"triage","ffffff",3436,"useOverlay props type lost","2025-03-28T21:05:02Z","https://github.com/nuxt/ui/issues/3436",0.7617186,{"description":2065,"labels":2066,"number":1998,"owner":1985,"repository":2010,"state":2011,"title":2068,"updated_at":2069,"url":2070,"score":2003},"Blocked by #720 ",[2067],{"name":2028,"color":2029},"[Community] Nuxters filter to select community only","2022-07-25T13:34:54Z","https://github.com/nuxt/nuxt.com/issues/684",{"description":2072,"labels":2073,"number":2077,"owner":1985,"repository":2046,"state":2011,"title":2078,"updated_at":2079,"url":2080,"score":2081},"### Description\n\nEnhance UTabs by making the tab header sticky while allowing the content area to be scrollable. This ensures better usability, keeping the tabs visible while navigating long content.\n\n### Additional context\n\n_No response_",[2074,2076],{"name":2028,"color":2075},"a2eeef",{"name":2043,"color":2044},3330,"feat(UTabs): Sticky Tab header and Scrollable content","2025-02-17T18:21:54Z","https://github.com/nuxt/ui/issues/3330",0.7696637,{"description":2083,"labels":2084,"number":2085,"owner":1985,"repository":1986,"state":2011,"title":2086,"updated_at":2087,"url":2088,"score":2089},"```\n[info] Building client...\n[info] vite v6.1.0 building for production...\n[info] transforming...\n[info] ✓ 355 modules transformed.\n[error] x Build failed in 6.03s\n[error] [nuxi] Nuxt Build Error: [nuxt:fonts:font-family-injection] fetch failed\nfile: /vercel/path0/assets/css/tailwind.css\n at node:internal/deps/undici/undici:13502:13\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async fromUrl (node_modules/@capsizecss/unpack/dist/index.mjs:281:20)\n at async readMetrics (node_modules/fontaine/dist/index.mjs:120:82)\n at async generateFontFallbacks (node_modules/@nuxt/fonts/dist/module.mjs:44:67)\n at async addFontFaceDeclaration (node_modules/@nuxt/fonts/dist/module.mjs:380:38)\n at async Promise.all (index 14)\n at async transformCSS (node_modules/@nuxt/fonts/dist/module.mjs:449:5)\n at async Object.transform (node_modules/@nuxt/fonts/dist/module.mjs:461:17)\n at async transform (node_modules/rollup/dist/es/shared/node-entry.js:20698:16)\n [cause]: \n at internalConnectMultiple (node:net:1122:18)\n at internalConnectMultiple (node:net:1190:5)\n at Timeout.internalConnectMultipleTimeout (node:net:1716:5)\n```\n\n**Steps to re-produce**\n\n1. Add Nuxtjs/fonts (0.11.0) to existing Nuxt (3.15.4) project.\n2. Commit and merge to repo.\n3. Vercels run the build automatically\n\n**Expected**: It should work and deploy new version of mywebsite.\n**Actual**: Build fails\n\nI added the @nuxt/fonts module to my Nuxt project, but now my Vercel builds are failing.\n\nI’ve already added the module to the modules array in nuxt.config.ts. I followed the setup from the Tailwind v3 example.\n\nAny ideas on what might be causing the build failure? Here’s my tailwind.config.ts:\n\n```\n{\n theme: {\n ...\n },\n extend: {\n fontFamily: {\n title: ['Geist'],\n text: ['Geist Mono']\n }\n }\n}\n```",[],577,"Vercel build fails","2025-03-21T04:10:51Z","https://github.com/nuxt/fonts/issues/577",0.7697014,["Reactive",2091],{},["Set"],["ShallowReactive",2094],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"TUv1Gc9ZlTotMMXczYDXn6tOC-HNmApKmZk2IsfNCxY":-1},"/nuxt/nuxt.com/1003"]