`\nThis props was available on Nuxt UI V2.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2901,2904,2905],{"name":2902,"color":2903},"bug","d73a4a",{"name":2871,"color":2872},{"name":2874,"color":2875},3703,"closed","Missing Container UI props","2025-03-27T09:43:56Z","https://github.com/nuxt/ui/issues/3703",0.75363815,{"description":2913,"labels":2914,"number":2915,"owner":2877,"repository":2916,"state":2907,"title":2917,"updated_at":2918,"url":2919,"score":2920},"Hi 👋 \r\nI am attempting to use `@nuxt/test-utils` on a fresh nuxt-project.\r\nHowever, the setup function throws with the following message: \r\n`No 'pages' directory found in \u003CPATH-TO-MY-PROJECT>/test/fixture. Did you mean to run 'nuxt' in the parent ('../') directory?`\r\n\r\nI have tried to pass `configFile` and `rootDir` with path values relative to the test file. \r\nIs this a bug or am I doing something wrong? \r\n\r\nAll help is greatly appreciated 😄 \r\n \r\nHere is the relevant code: \r\n```ts\r\n// \u003CPATH-TO-MY-PROJECT>/test/pages/index.test.ts\r\nimport { setupTest } from '@nuxt/test-utils'\r\n\r\ndescribe(\"The index page\", () => {\r\n\r\n setupTest({ server: true /*, configFile: \"../../nuxt.config.js\", rootDir: \"../../\" */});\r\n});\r\n```\r\n```ts\r\n// \u003CPATH-TO-MY-PROJECT>/jest.config.ts\r\n// jest.config.ts\r\nimport type { Config } from '@jest/types';\r\n\r\n// Sync object\r\nconst config: Config.InitialOptions = {\r\n verbose: true,\r\n preset: \"@nuxt/test-utils\",\r\n};\r\nexport default config;\r\n```",[],477,"test-utils","Setup throws \"no 'pages' directory found\"","2023-12-02T00:13:13Z","https://github.com/nuxt/test-utils/issues/477",0.75457174,{"description":2922,"labels":2923,"number":2924,"owner":2877,"repository":2916,"state":2907,"title":2925,"updated_at":2926,"url":2927,"score":2928},"When updating from 3.0.0.rc9 to 3.3.1 I see this error:\r\n\r\n```\r\n ERROR TypeError: filters.some is not a function 16:18:54\r\n\r\n ❯ node_modules/vitest/dist/chunk-vite-node-externalize.6956d2d9.mjs:10719:51 16:18:54\r\n ❯ Vitest.globTestFiles node_modules/vitest/dist/chunk-vite-node-externalize.6956d2d9.mjs:10719:29 16:18:54\r\n ❯ process.processTicksAndRejections node:internal/process/task_queues:95:5 16:18:54\r\n ❯ Vitest.start node_modules/vitest/dist/chunk-vite-node-externalize.6956d2d9.mjs:10472:50 16:18:54\r\n ❯ startVitest node_modules/vitest/dist/chunk-vite-node-externalize.6956d2d9.mjs:11204:5 16:18:54\r\n ❯ runTests node_modules/@nuxt/test-utils/dist/index.mjs:311:21 16:18:54\r\n ❯ Object.invoke node_modules/nuxi/dist/chunks/test.mjs:14:5 16:18:54\r\n ❯ _main node_modules/nuxi/dist/cli.mjs:49:20 \r\n```",[],418,"TypeError: filters.some is not a function ","2023-12-02T00:13:09Z","https://github.com/nuxt/test-utils/issues/418",0.75683355,{"description":2930,"labels":2931,"number":2935,"owner":2877,"repository":2878,"state":2907,"title":2936,"updated_at":2937,"url":2938,"score":2939},"### Environment\n\n- Operating System: `Linux`\n- Node Version: `v22.14.0`\n- Nuxt Version: `3.16.2`\n- CLI Version: `3.24.0`\n- Nitro Version: `2.11.8`\n- Package Manager: `npm@11.1.0`\n- Builder: `-`\n- User Config: `devtools`, `compatibilityDate`, `app`, `css`, `vite`, `ui`, `runtimeConfig`, `modules`, `i18n`\n- Runtime Modules: `@nuxt/image@1.10.0`, `@nuxt/eslint@1.3.0`, `@nuxtjs/i18n@9.4.0`, `@nuxt/ui@3.0.2`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.2\n\n### Reproduction\n\nn/a\n\n### Description\n\nIt seems to me that the RadioGroup component doesnt really come with variant or indicator props even though its described in the documentation. Even when chaning it to all available options, nothing changes.\n\nI also checked source files and it appears to not be there as well.\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2932,2933,2934],{"name":2902,"color":2903},{"name":2871,"color":2872},{"name":2874,"color":2875},3765,"variant, indicator and some other props missing in RadioGroup","2025-04-01T15:20:27Z","https://github.com/nuxt/ui/issues/3765",0.7580944,{"description":2941,"labels":2942,"number":2947,"owner":2877,"repository":2878,"state":2907,"title":2948,"updated_at":2949,"url":2950,"score":2951},"### Description\n\nI use vitejs and @nuxt/ui 3.0.2 and I need to use the icons locally. \n\nI did not find any configuration options in the documentation.\n\nI tried installing @iconify-json/lucide packages, etc. and configuring the config from @nuxt/icons. There is no result yet. Do you have any ideas?",[2943,2946],{"name":2944,"color":2945},"question","d876e3",{"name":2871,"color":2872},3965,"How can I set up icons locally?","2025-04-24T09:10:46Z","https://github.com/nuxt/ui/issues/3965",0.7817948,{"description":2953,"labels":2954,"number":2957,"owner":2877,"repository":2878,"state":2907,"title":2958,"updated_at":2959,"url":2960,"score":2961},"### Description\n\nFaced with such a problem that if there are enough divs in the modal window, then the modal window acquires a shell bar. \n\nThe question is, is it possible to customize the scrollbar inside the modal window?.\n\nI tried to write shell styles inside the ui settings, or in the app.config.ts style separately for modal, but nothing worked.\n\nI am using Nuxt UI 3 (3.0.0-beta.2).\n\n```\n\u003CUModal\n :title=\"`edit product ${props.product.name}`\"\n description=\"text text text text text text text text text text text text text text text!\"\n :ui=\"{\n content: 'w-[600px] max-w-full modal-body-scroll',\n body: 'modal-body-scroll',\n title: 'text-(--ui-primary)'\n }\"\n > \n //content divs\n\u003C/UModal>\n\n\n//Test style in the modal-body-scroll class\n\u003Cstyle scoped>\n.modal-body-scroll {\n max-height: 20px;\n overflow-y: auto;\n scrollbar-width: thin;\n scrollbar-color: #6c6c6f transparent;\n}\n\n.modal-body-scroll::-webkit-scrollbar {\n width: 8px;\n}\n\n.modal-body-scroll::-webkit-scrollbar-thumb {\n background-color: #6c6c6f;\n border-radius: 4px;\n}\n\n.modal-body-scroll::-webkit-scrollbar-track {\n background: transparent;\n}\n\u003C/style>\n```\n\n\n\n\n",[2955,2956],{"name":2944,"color":2945},{"name":2871,"color":2872},3459,"scroll in the modal","2025-03-09T12:25:08Z","https://github.com/nuxt/ui/issues/3459",0.78264946,{"description":2963,"labels":2964,"number":2966,"owner":2877,"repository":2878,"state":2907,"title":2967,"updated_at":2968,"url":2969,"score":2970},"### For what version of Nuxt UI are you asking this question?\n\nv2.x\n\n### Description\n\nHello, first of all thank you for your fairly complete UI modules! \n\nI'm trying to do multi-line with the slot option of your UTooltip component, unfortunately it only displays the first line. \n\nIs it possible to do this ? Do you have a use case to show me please ?\n\nThank you in advance !",[2965],{"name":2944,"color":2945},2530,"Multi-line of UTooltip Component","2024-11-06T16:43:15Z","https://github.com/nuxt/ui/issues/2530",0.78343904,{"description":2972,"labels":2973,"number":2977,"owner":2877,"repository":2878,"state":2907,"title":2978,"updated_at":2979,"url":2980,"score":2981},"### Description\n\n\n## 🔧 Current Behavior\n\nThe `deferInputValidation` parameter in `useFormField` is currently hardcoded in the `Input` component:\n\n```ts\nconst { emitFormBlur, emitFormInput, /* ... */ } = useFormField\u003CInputProps>(props, { \n deferInputValidation: false // Hardcoded\n})\n```\n\nThis limits flexibility, as consumers of the `Input` component cannot control validation timing behavior (e.g., validate on blur vs. validate on input).\n\n## ✅ Proposed Solution\n\nMake `deferInputValidation` configurable via a component prop:\n\n1. **Pass dynamic value to `useFormField`:**\n\n```ts\nuseFormField\u003CInputProps>(props, {\n deferInputValidation: props.deferInputValidation\n})\n```\n\n2. **Update the component props interface:**\n\n```ts\ndeferInputValidation?: boolean\n```\n\n---\n\n## 💡 Use Cases\n\n- **Delayed validation** for complex, interdependent form fields \n- **Immediate validation** for sensitive or critical fields \n- Flexibility for UX patterns like **\"validate-on-blur\"** or **\"validate-as-you-type\"**\n\n---\n\n## 🔁 Alternatives Considered\n\n- **Wrapper Component**: Adds unnecessary complexity \n- **Global Form-Level Config**: Less flexible than per-field control\n\n---\n\n## 🧪 Testing Impact\n\n- Covered by existing validation tests with both `true` and `false` cases\n\n---\n\n## 📚 Documentation\n\nRequires updates to:\n\n- Component prop API \n- Form validation best practices\n\n---\n\n## ⚙️ Why This Matters\n\nThis change supports **Inversion of Control** — empowering component consumers to control validation timing based on specific UX needs.\n```\n\n### Additional context\n\n_No response_",[2974,2975,2976],{"name":2868,"color":2869},{"name":2871,"color":2872},{"name":2874,"color":2875},3810,"[UForm] Feature Request: Make deferInputValidation Configurable in useFormField","2025-04-20T15:25:42Z","https://github.com/nuxt/ui/issues/3810",0.7869547,["Reactive",2983],{},["Set"],["ShallowReactive",2986],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fYNwBAyr4L9iQ9J5sgBSHRV-YBY9GPPVKDGTQGaVJLtQ":-1},"/nuxt/ui/3680"]