\n \u003C/UCarousel>\n\u003C/template>\n```\n\nAnd I get some TypeScript errors:\n\nProperty 'page' does not exist on type 'CreateComponentPublicInstanceWithMixins(...)\nProperty 'select' does not exist on type 'CreateComponentPublicInstanceWithMixins(...)\nProperty 'next' does not exist on type 'CreateComponentPublicInstanceWithMixins(...)\n\nHow should I correctly infer the type for UCarousel?\n\nNuxt v3.15.1\nNuxtUI v2.20.0",[3045],{"name":3046,"color":3047},"question","d876e3",3053,"closed","How to properly use UCarousel API with TypeScript","2025-04-22T13:44:43Z","https://github.com/nuxt/ui/issues/3053",0.69053876,{"description":3055,"labels":3056,"number":3061,"owner":3020,"repository":3037,"state":3049,"title":3062,"updated_at":3063,"url":3064,"score":3065},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.15.1\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.7.0\n- Builder: -\n- User Config: compatibilityDate, devtools, colorMode, css, modules, supabase, app\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.12, @nuxtjs/supabase@1.4.6, @nuxt/image@1.9.0, @pinia/nuxt@0.10.1, pinia-plugin-persistedstate/nuxt@4.2.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.13\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/s7wlqy\n\n### Description\n\nThe UAlert component prop \"orientation\" does not work when set to horizontal. It stays in the default vertical mode in both my local env and the sandbox.\n\n### Additional context\n\n\n\nhttps://ui3.nuxt.dev/components/alert#orientation\n\n### Logs\n\n```shell-script\n\n```",[3057,3058],{"name":3031,"color":3032},{"name":3059,"color":3060},"v3","49DCB8",3370,"UAlert component orientation prop not working","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3370",0.6963247,{"description":3067,"labels":3068,"number":3074,"owner":3020,"repository":3037,"state":3049,"title":3075,"updated_at":3076,"url":3077,"score":3078},"### Description\n\nBreadcrumb uses Link (and LinkBase) to implement the item rendering and navigation. Link (through LinkBase) in itself supports `onClick` event/prop. Now, passing `onClick` to the breadcrumb item does not go all the way through to the LinkBase, and thus prevents the fine-grained control of the Breadcrumb component.\n\nThe usage would look something like this:\n```\n\u003Ctemplate>\n \u003CUBreadcrumb :items=\"items\" />\n\u003C/template>\n\u003Cscript setup>\nconst items = [\n { label: \"click for one\", onClick: () => alert(\"1\"), to: \"/one\" },\n { label: \"click for two\", onClick: () => alert(\"2\"), to: \"/two\" },\n]\n\u003C/script>\n```\n\nMy need is to have some secondary effects happening besides the navigation when the user clicks on a breadcrumb item.\n\n### Additional context\n\n_No response_",[3069,3072,3073],{"name":3070,"color":3071},"enhancement","a2eeef",{"name":3059,"color":3060},{"name":3034,"color":3035},3631,"Support for `onClick` event on Breadcrumb items","2025-03-24T18:08:16Z","https://github.com/nuxt/ui/issues/3631",0.7098971,{"description":3080,"labels":3081,"number":3085,"owner":3020,"repository":3086,"state":3049,"title":3087,"updated_at":3088,"url":3089,"score":3090},"### Environment\n\n- Operating System: Windows_NT\r\n- Node Version: v18.19.0\r\n- Nuxt Version: 3.11.1\r\n- CLI Version: 3.11.1\r\n- Nitro Version: 2.9.4\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: devtools, modules\r\n- Runtime Modules: @nuxt/test-utils/module\n\n### Reproduction\n\nhttps://github.com/chronicadventure/nuxt-bug\r\n\r\njust run `npm test` and the console will error out. *Note* you don't even need an actual test, just the import causes the entire file to fail.\n\n### Describe the bug\n\nImporting `import { mockNuxtImport } from '@nuxt/test-utils/runtime'` as stated in the docs causes the entire test file to fail.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nDEV v1.4.0 C:/Users/AdrianCampos/BugRepo/repro\r\n\r\n ❯ tests/random.nuxt.test.js (0)\r\n\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Suites 1 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\n\r\n FAIL tests/random.nuxt.test.js [ tests/random.nuxt.test.js ]\r\nError: Failed to load url #imports (resolved id: #imports) in C:/Users/AdrianCampos/BugRepo/node_modules/@nuxt/test-utils/dist/runtime-utils/index.mjs. Does the file exist?\r\n ❯ loadAndTransform ../node_modules/vite/dist/node/chunks/dep-B-u6xNiR.js:53832:21\r\n\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯\r\n\r\n Test Files 1 failed (1)\r\n Tests no tests\r\n Start at 21:58:52\r\n Duration 2.22s (transform 69ms, setup 0ms, collect 0ms, tests 0ms, environment 0ms, prepare 846ms)\r\n\r\n\r\n FAIL Tests failed. Watching for file changes...\r\n press h to show help, press q to quit\n```\n",[3082],{"name":3083,"color":3084},"pending triage","5D08F5",800,"test-utils","Failed to load url #imports after importing mockNuxtImport","2024-05-26T19:14:39Z","https://github.com/nuxt/test-utils/issues/800",0.7099669,{"description":3092,"labels":3093,"number":3096,"owner":3020,"repository":3037,"state":3049,"title":3097,"updated_at":3098,"url":3099,"score":3100},"### Environment\n\n-\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.16.0\n\n### Reproduction\n\n- \n\n### Description\n\nUpgraded all deps to the latest and bam Nuxt 3.16.0 is added. We get errors now as Nuxt UI 3 still ships with\n\n`'@unhead/vue': 1.11.20(vue@3.5.13(typescript@5.8.2))\n`\n\nAs of Nuxt 3.16.0 ships with @unhead2:\nhttps://nuxt.com/blog/v3-16#unhead-v2\n\nActual error:\n`[@nuxt/scripts 9:42:20 PM] ERROR Nuxt Scripts requires Unhead >= 2, you are using v1.11.20. Please run nuxi upgrade --clean to upgrade...`\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3094,3095],{"name":3031,"color":3032},{"name":3059,"color":3060},3513,"Nuxt 3.16.0 - ships with @unhead2","2025-03-10T08:49:36Z","https://github.com/nuxt/ui/issues/3513",0.7117438,{"description":3102,"labels":3103,"number":3108,"owner":3020,"repository":3037,"state":3049,"title":3109,"updated_at":3110,"url":3111,"score":3112},"### Environment\r\n\r\n- \"@nuxt/ui\": \"^2.18.6\",\r\n- \"nuxt\": \"^3.13.2\",\r\n- \"vue\": \"^3.5.10\",\r\n\r\n### Version\r\n\r\nv2.18.6\r\n\r\n### Reproduction\r\n\r\nhttps://github.com/guirak/NuxtUiTailwindContentPurgedAtFirstLaunch\r\n\r\n### Description\r\n\r\nHello,\r\n\r\nI'm having a important nuxt ui mono repo project and I'm encountering problems with nuxt/ui since version 6.12.0 of @nuxtjs/tailwindcss. \r\n\r\nI was forced to stay in an old version of nuxt/ui to don't have the problem : \r\n\r\n```\r\n \"pnpm\": {\r\n \"overrides\": {\r\n \"@nuxtjs/tailwindcss\": \"6.11.4\",\r\n \"@nuxt/ui\": \"2.15.2\"\r\n }\r\n },\r\n```\r\n\r\n# What happens ? \r\n\r\nAt first launch, css classes used in nuxt ui components are not correctly taken into account. \r\nIt's necessary to restart a second time the app to have the correct display\r\n\r\nThe bug is present since the version 6.12.0 of nuxtjs/tailwindcss. Maybe some effect of the First Class HMR.\r\n\r\n## Step to reproduce \r\n\r\nThe code at the following link is a minimal reproduction of my project structure : https://github.com/guirak/NuxtUiTailwindContentPurgedAtFirstLaunch\r\n\r\n- From the root project path, launch the following command : \r\n\r\n```bash\r\n# Clear the build \r\n./scripts/CleanProject.bash\r\n\r\n# Install and prepare \r\npnpm i; pnpm run dev:prepare\r\n\r\n# Launch the app\r\ncd apps/mmi-order-front-office\r\npnpm run dev\r\n```\r\n\r\n**The tailwind classes used in apps and modules are correctly displayed but the tailwind classes defined in the nuxt-ui components are not taken into account.**\r\n\r\n\r\n\r\n- Stop and restart the server\r\n\r\n```bash\r\npnpm run dev\r\n```\r\n\r\n**All tailwind classes are correctly taken into account.**\r\n\r\n\r\n\r\n\r\n\r\nThe problem is present too when building the prod version with **pnpm run build**\r\n\r\n\r\nThe problem seems to happens when using nuxt ui in a nuxt module. Please, have you any ideas, to solve this problem. \r\n\r\n\r\nThank you\r\n\r\n\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3104,3105],{"name":3031,"color":3032},{"name":3106,"color":3107},"upstream","78bddb",2282,"Since Tailwind First Class HMR, nuxt-ui components css classes not taken into account at first launch","2024-10-18T09:16:15Z","https://github.com/nuxt/ui/issues/2282",0.71561044,{"description":3114,"labels":3115,"number":3116,"owner":3020,"repository":3021,"state":3049,"title":3117,"updated_at":3118,"url":3119,"score":3120},"Since this commit 36e38c32f8f1f61570080e4e95f51cf249229a1a (I guess), when I open pm2 logs, I get a lot of console.log from nuxt icon\n\n\nIs there a way to disable it?",[],299,"Disable console.log","2024-11-19T01:11:23Z","https://github.com/nuxt/icon/issues/299",0.71607834,{"description":3122,"labels":3123,"number":3124,"owner":3020,"repository":3125,"state":3049,"title":3126,"updated_at":3127,"url":3128,"score":3129},"We can take the code and do exactly like on Volta to display the list of shortcuts as the list starts to grow.",[],693,"nuxt.com","[Project] Shortcuts slideover","2023-02-15T12:32:44Z","https://github.com/nuxt/nuxt.com/issues/693",0.71612644,["Reactive",3131],{},["Set"],["ShallowReactive",3134],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fzBXYrkDX0GpXa3y1ttNXgcUAiWqVL08jlWmjIdHTicY":-1},"/nuxt/ui/2894"]