| \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.72345835,{"description":2876,"labels":2877,"number":2881,"owner":2868,"repository":2882,"state":2870,"title":2883,"updated_at":2884,"url":2885,"score":2886},"### 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",[2878],{"name":2879,"color":2880},"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.7666667,{"description":2888,"labels":2889,"number":2892,"owner":2868,"repository":2893,"state":2894,"title":2895,"updated_at":2896,"url":2897,"score":2898},"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",[2890],{"name":2879,"color":2891},"ff281a",1041,"nuxt.com","closed","[Jobs] Error after API update","2023-06-06T12:14:28Z","https://github.com/nuxt/nuxt.com/issues/1041",0.7260956,{"description":2900,"labels":2901,"number":2906,"owner":2868,"repository":2907,"state":2894,"title":2908,"updated_at":2909,"url":2910,"score":2911},"### 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",[2902,2903],{"name":2879,"color":2880},{"name":2904,"color":2905},"v3","49DCB8",2906,"ui","v3: Missing translations","2025-01-25T13:12:21Z","https://github.com/nuxt/ui/issues/2906",0.74683106,{"description":2913,"labels":2914,"number":2921,"owner":2868,"repository":2893,"state":2894,"title":2922,"updated_at":2923,"url":2924,"score":2925},"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) ?",[2915,2918],{"name":2916,"color":2917},"enhancement","1ad6ff",{"name":2919,"color":2920},"marketing","f5c828",1048,"[Agencies] Present agencies in a random order","2023-10-10T14:45:03Z","https://github.com/nuxt/nuxt.com/issues/1048",0.7500736,{"description":2927,"labels":2928,"number":2929,"owner":2868,"repository":2893,"state":2894,"title":2930,"updated_at":2931,"url":2932,"score":2933},"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.7533286,{"description":2935,"labels":2936,"number":2939,"owner":2868,"repository":2907,"state":2894,"title":2940,"updated_at":2941,"url":2942,"score":2943},"### Environment\n\n Operating System: Linux\n- Node Version: v20.15.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.7.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxtjs/i18n@9.1.1, @nuxt/ui@3.0.0-alpha.10, @pinia/nuxt@0.9.0, nuxt-viewport@2.2.0, @nuxthub/core@0.8.7, nuxt-auth-utils@0.5.6, @nuxt/fonts@0.10.3\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.10\n\n### Reproduction\n\n```vue\n//dont work\n\u003CUSelect variant=\"none\" class=\"w-full\" label-key=\"name\" value-key=\"id\" multiple\n @update:model-value=\"testFunctionArray\" @change=\"testFunctionArray\"\n v-model=\"row.original.permissionsModel\" :items=\"permissions\">\n\u003C/USelect>\n```\n\n```vue\n//work fine\n\u003CUSelect variant=\"none\" class=\"w-full\" label-key=\"name\" value-key=\"id\"\n @update:model-value=\"testFunction\" @change=\"testFunction\"\n v-model=\"row.original.permissionModel\" :items=\"permissions\">\n\u003C/USelect>\n```\n\n### Description\n\n`testFunctionArray` is never called if multiple prop is set to true\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2937,2938],{"name":2879,"color":2880},{"name":2904,"color":2905},2953,"USelect with multiple prop does not trigger event when model-value change","2025-01-25T13:12:19Z","https://github.com/nuxt/ui/issues/2953",0.7565943,{"labels":2945,"number":2956,"owner":2868,"repository":2868,"state":2894,"title":2957,"updated_at":2958,"url":2959,"score":2960},[2946,2949,2950,2953],{"name":2947,"color":2948},"3.x","29bc7f",{"name":2879,"color":2880},{"name":2951,"color":2952},"nitro","bfd4f2",{"name":2954,"color":2955},"🔨 p3-minor","FBCA04",13230,"Filename casing breaks ./server/api ","2023-01-19T16:49:12Z","https://github.com/nuxt/nuxt/issues/13230",0.75774014,{"description":2962,"labels":2963,"number":2965,"owner":2868,"repository":2907,"state":2894,"title":2966,"updated_at":2967,"url":2968,"score":2969},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v22.3.0`\r\n- Nuxt Version: `3.13.1`\r\n- CLI Version: `3.13.1`\r\n- Nitro Version: `2.9.7`\r\n- Package Manager: `yarn@1.22.22`\r\n- Builder: `-`\r\n- User Config: `compatibilityDate`, `devtools`, `modules`, `plugins`, `runtimeConfig`, `i18n`\r\n- Runtime Modules: `@nuxt/ui@2.18.4`, `@nuxtjs/i18n@8.5.1`\r\n- Build Modules: `-`\r\n\n\n### Version\n\nv2.18.4\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-jfdc58?file=app.vue,app.config.ts\n\n### Description\n\n## Description\r\nThe Nuxt UI notification component is currently being created and added to the DOM even when no toast has been triggered. This behavior leads to unintended consequences due to the component's z-index:\r\n\r\nThe notification component occupies part of the screen unnecessarily.\r\nIt overlaps other elements on the page due to its z-index, potentially disrupting the user interface.\r\n\r\n## Expected Behavior\r\nThe notification component should only be created and added to the DOM when a toast is actually triggered.\r\n\r\n## Current Behavior\r\nThe notification component is always present in the DOM, regardless of whether a toast has been triggered or not.\r\n\r\n## Steps to Reproduce\r\n\r\n- Implement the Nuxt UI notification component in a project.\r\n- Inspect the DOM without triggering any toasts.\r\n- Observe that the notification component is present and has a z-index applied.\r\n\r\n## Additional Context\r\nThis issue affects the usability and performance of applications using the Nuxt UI notification component. Resolving it would improve both the user experience and the overall efficiency of the component.\r\n\r\n## Possible Solution\r\nConsider implementing a conditional rendering approach where the notification component is only added to the DOM when it's actually needed (i.e., when a toast is triggered).\r\n\u003Cimg width=\"1427\" alt=\"Screenshot 2024-09-04 at 6 29 00 PM\" src=\"https://github.com/user-attachments/assets/da90352f-71e6-4aaf-9bda-7a9e4a3fd056\">\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2964],{"name":2879,"color":2880},2113,"Notification component created even when toast is not triggered, causing z-index issues","2024-11-09T10:24:37Z","https://github.com/nuxt/ui/issues/2113",0.764522,{"description":2971,"labels":2972,"number":2980,"owner":2868,"repository":2868,"state":2894,"title":2981,"updated_at":2982,"url":2983,"score":2984},"### Environment\n\nNetlify preview, branch and production\n\n### Reproduction\n\nWhen you create a new deployment on netlify it returns:\r\n\u003Cimg width=\"859\" alt=\"image\" src=\"https://user-images.githubusercontent.com/79509387/211893011-8eda2e32-5978-4ea4-84e3-3d622453547e.png\">\r\n\r\nThere are numerous others complaint about it on Netllify, but Netlify points towards Nuxt\r\n\r\n\r\nhttps://answers.netlify.com/t/this-function-has-crashed-nuxt-3-production/83046\n\n### Describe the bug\n\n\u003Cimg width=\"859\" alt=\"image\" src=\"https://user-images.githubusercontent.com/79509387/211893168-ce2f0710-7be6-4171-9611-61590b2edcb6.png\">\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2973,2974,2977],{"name":2947,"color":2948},{"name":2975,"color":2976},"pending triage","E99695",{"name":2978,"color":2979},"upstream-bug","B60205",12373,"Runtime.ImportModuleError - Error: Cannot find module 'server' Require stack: - /var/runtime/index.mjs","2023-01-19T16:13:52Z","https://github.com/nuxt/nuxt/issues/12373",0.7657492,["Reactive",2986],{},["Set"],["ShallowReactive",2989],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fTUv1Gc9ZlTotMMXczYDXn6tOC-HNmApKmZk2IsfNCxY":-1},"/nuxt/nuxt.com/1003"]