| \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.79930234,{"description":2874,"labels":2875,"number":2885,"owner":2866,"repository":2886,"state":2868,"title":2887,"updated_at":2888,"url":2889,"score":2890},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v18.20.3\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: npm@10.2.3\r\n- Builder: -\r\n- User Config: compatibilityDate, devtools, extends, modules\r\n- Runtime Modules: @nuxt/ui@2.18.4\r\n- Build Modules: -\n\n### Version\n\n2.18.4\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-qsqtmc?file=app.vue\n\n### Description\n\nLandingFAQ being built on top Accordion, when an item has a specified \"slot\" property, it should allow to display custom content in a corresponding slot. In my reproduction, you can see i have an faq item with a slot property equal to \"risks\". When using \u003Ctemplate #risks> risks \u003C/template> to show a specific content for that item, it works well in the accordion but is ignored in the LandingFAQ where the content property is shown instead.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2876,2879,2882],{"name":2877,"color":2878},"bug","d73a4a",{"name":2880,"color":2881},"pro","5BD3CB",{"name":2883,"color":2884},"triage","ffffff",2057,"ui","LandingFAQ component in Pro ignores the \"slot\" property of an item","2024-09-10T20:23:57Z","https://github.com/nuxt/ui/issues/2057",0.80132294,{"description":2892,"labels":2893,"number":2894,"owner":2866,"repository":2867,"state":2895,"title":2896,"updated_at":2897,"url":2898,"score":2899},"Now that TailwindCSS v4 is going stable, we should better support it.\n\n- [x] **Playground**: Add TailwindCSS v4 example. It'd be ideal if we can find a way to keep v3 and v4 in one npm project.\n- [x] **Test**: Test for TailwindCSS v4\n- [ ] Auto enable `experimental.processCSSVariables` if Tailwind v4 is detected (i.e. `@tailwindcss/vite` is installed)",[],468,"closed","TailwindCSS v4","2025-03-10T13:13:24Z","https://github.com/nuxt/fonts/issues/468",0.7754562,{"description":2901,"labels":2902,"number":2910,"owner":2866,"repository":2911,"state":2895,"title":2912,"updated_at":2913,"url":2914,"score":2915},"### Environment\n\nReproduction: https://stackblitz.com/edit/github-gu1sj1-xq3xf8?file=tests%2Fe2e%2Fbasic.e2e.test.ts\r\n\r\nA minimal repo with just [vitest](https://github.com/vitest-dev/vitest) and [@nuxt/test-utils](https://github.com/nuxt/test-utils), an app.vue, and a `pages/index.vue` fails with error:\r\n\r\n```js\r\n❯ npm run test\r\n\r\n> test\r\n> vitest\r\n\r\nRunning with compatibility version `4`\r\n\r\n DEV v1.6.0 /home/projects/github-gu1sj1-xq3xf8/app\r\n\r\n ❯ ../tests/e2e/basic.e2e.test.ts (1)\r\n ❯ basic (1)\r\n ⠹ [ beforeAll ]\r\n · contains Welcome to Nuxt! string\r\n\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Suites 1 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\n\r\n FAIL ../tests/e2e/basic.e2e.test.ts > basic\r\nError: Cannot find any nuxt version from ./app\r\n ❯ Module.loadNuxt ../node_modules/@nuxt/kit/dist/index.mjs:2729:11\r\n ❯ loadFixture ../node_modules/@nuxt/test-utils/dist/shared/test-utils.C7cWLW4C.mjs:102:14\r\n 100| });\r\n 101| const buildDir = ctx.nuxt.options.buildDir;\r\n 102| if (!existsSync(buildDir)) {\r\n | ^\r\n 103| await promises.mkdir(buildDir, { recursive: true });\r\n 104| ctx.teardown = ctx.teardown || [];\r\n ❯ setup2 ../node_modules/@nuxt/test-utils/dist/shared/test-utils.C7cWLW4C.mjs:178:7\r\n\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯\r\n\r\n Test Files 1 failed (1)\r\n Tests (1)\r\n Start at 09:54:14\r\n Duration 4.84s (transform 445ms, setup 45ms, collect 2.14s, tests 5ms, environment 0ms, prepare 807ms)\r\n```\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-gu1sj1-xq3xf8?file=tests%2Fe2e%2Fbasic.e2e.test.ts\n\n### Describe the bug\n\nCannot successfully end-to-end test if there is a pages directory with an index.vue.\n\n### Additional context\n\n```\r\n\"dependencies\": {\r\n \"@nuxt/test-utils\": \"^3.13.1\",\r\n \"nuxt\": \"^3.12.3\",\r\n \"vitest\": \"^1.4.0\",\r\n \"vue\": \"latest\"\r\n }\r\n```\n\n### Logs\n\n```shell-script\n❯ npm run test\r\n\r\n> test\r\n> vitest\r\n\r\nRunning with compatibility version `4`\r\n\r\n DEV v1.6.0 /home/projects/github-gu1sj1-xq3xf8/app\r\n\r\n ❯ ../tests/e2e/basic.e2e.test.ts (1)\r\n ❯ basic (1)\r\n ⠹ [ beforeAll ]\r\n · contains Welcome to Nuxt! string\r\n\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Suites 1 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\n\r\n FAIL ../tests/e2e/basic.e2e.test.ts > basic\r\nError: Cannot find any nuxt version from ./app\r\n ❯ Module.loadNuxt ../node_modules/@nuxt/kit/dist/index.mjs:2729:11\r\n ❯ loadFixture ../node_modules/@nuxt/test-utils/dist/shared/test-utils.C7cWLW4C.mjs:102:14\r\n 100| });\r\n 101| const buildDir = ctx.nuxt.options.buildDir;\r\n 102| if (!existsSync(buildDir)) {\r\n | ^\r\n 103| await promises.mkdir(buildDir, { recursive: true });\r\n 104| ctx.teardown = ctx.teardown || [];\r\n ❯ setup2 ../node_modules/@nuxt/test-utils/dist/shared/test-utils.C7cWLW4C.mjs:178:7\r\n\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯\r\n\r\n Test Files 1 failed (1)\r\n Tests (1)\r\n Start at 09:54:14\r\n Duration 4.84s (transform 445ms, setup 45ms, collect 2.14s, tests 5ms, environment 0ms, prepare 807ms)\n```\n",[2903,2904,2907],{"name":2877,"color":2878},{"name":2905,"color":2906},"vitest-environment","b60205",{"name":2908,"color":2909},"pending triage","5D08F5",895,"test-utils","Adding `/pages/index.vue` breaks e2e testing","2024-07-18T14:13:18Z","https://github.com/nuxt/test-utils/issues/895",0.78427947,{"description":2917,"labels":2918,"number":2920,"owner":2866,"repository":2911,"state":2895,"title":2921,"updated_at":2922,"url":2923,"score":2924},"I can't find a valid combination to use with Vuetify. I created an issue at `@nuxt-alt/vuetify`, where the `vite-plugin-vuetify` causes error `Vuetify plugin must be loaded after the vue plugin`:\r\n* https://github.com/nuxt-alt/vuetify/issues/9\r\n\r\nThis is caused by `vite:extendConfig` Nuxt hook not having the `vite:vue` Plugin accessible, so it can't reorder it. (Using `vite:configResolved` hook instead didn't work either.)\r\n\r\nNote that this issue only occurs when `vitest.config.mjs` is used, so I assume there may be some `nuxt-vitest`-specific zero-config Vite misconfiguration. I'd appreciate any hints about the root cause (or alternatives).",[2919],{"name":2905,"color":2906},591,"Incompatible with Vuetify","2023-12-02T00:27:10Z","https://github.com/nuxt/test-utils/issues/591",0.7859912,{"description":2926,"labels":2927,"number":2931,"owner":2866,"repository":2932,"state":2895,"title":2933,"updated_at":2934,"url":2935,"score":2936},"Strange selection https://www.notion.so/nuxt/Strange-selection-000b5d189a154f708a5059b3a180f758",[2928],{"name":2929,"color":2930},"a11y","2CD658",1085,"nuxt.com","[Review] HomeCompaniesCarousel","2023-01-04T13:47:35Z","https://github.com/nuxt/nuxt.com/issues/1085",0.78617316,{"description":2938,"labels":2939,"number":2940,"owner":2866,"repository":2932,"state":2895,"title":2941,"updated_at":2942,"url":2943,"score":2944},"",[],990,"[Docs] Add pagination","2023-04-04T08:06:43Z","https://github.com/nuxt/nuxt.com/issues/990",0.7888687,{"description":2946,"labels":2947,"number":2954,"owner":2866,"repository":2886,"state":2895,"title":2955,"updated_at":2956,"url":2957,"score":2958},"### Description\n\nThe Nuxt UI v2 dropdown has the option to open on hover or click. In v3 the only option available is click. \n\n\n\n### Additional context\n\n_No response_",[2948,2951],{"name":2949,"color":2950},"enhancement","a2eeef",{"name":2952,"color":2953},"v3","49DCB8",3322,"[DropdownMenu] (v3) missing mode prop for hover/click","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3322",0.7942272,{"description":2960,"labels":2961,"number":2964,"owner":2866,"repository":2932,"state":2895,"title":2965,"updated_at":2966,"url":2967,"score":2968},"- [x] `/modules`\n- [x] `/community/repositories`\n- [x] `/community/nuxters`\n- [x] `/community/partners`\n- [x] `/resources/showcases`",[2962],{"name":2949,"color":2963},"1ad6ff",612,"[Responsive] Aside filters selects on mobile should be full width","2023-02-15T12:32:38Z","https://github.com/nuxt/nuxt.com/issues/612",0.7972155,{"description":2970,"labels":2971,"number":2964,"owner":2866,"repository":2911,"state":2895,"title":2973,"updated_at":2974,"url":2975,"score":2968},"## Description\r\nTrying to follow the official documentation, I am adding a `test` config section in the `defineVitestConfig` and receive the following error:\r\n#### Object literal may only specify known properties, and 'test' does not exist in type 'InlineConfig'.ts(2353)\r\n",[2972],{"name":2905,"color":2906},"`test` config not found in nuxt-vitest","2023-12-02T17:18:50Z","https://github.com/nuxt/test-utils/issues/612",["Reactive",2977],{},["Set"],["ShallowReactive",2980],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fSEPxhmQmfq6lOhJcBp95O8FVFK0hj6xIbRa3staoc4w":-1},"/nuxt/nuxt.com/1096"]