\n \u003C/NuxtLayout>\n \u003C/UApp>\n\u003C/template>\n\u003Cscript setup lang=\"ts\">\nimport {TooltipProviderProps} from \"reka-ui\";\n\nconst tooltipProps : TooltipProviderProps = {\n delayDuration: 700,\n skipDelayDuration: 300,\n disableHoverableContent: false,\n disableClosingTrigger: false,\n disabled: false,\n ignoreNonKeyboardFocus: false,\n}\n\u003C/script>\n```\n**nuxt.config.ts**\n```\n// https://nuxt.com/docs/api/configuration/nuxt-config\nexport default defineNuxtConfig({\n compatibilityDate: '2024-11-01',\n ssr: false,\n srcDir: 'src',\n devtools: { enabled: true },\n modules: [\n '@nuxt/ui',\n '@pinia/nuxt',\n '@nuxt/image',\n 'nuxt-icons',\n '@nuxtjs/i18n',\n ],\n css: ['~/assets/css/main.css']\n})\n```\nI found that when Nuxt3 SSR is set to false, the tooltip and toast do not display, and the tooltip also reports an error of 500\n\nInjection `Symbol(TooltipProviderContext)` not found. Component must be used within `TooltipProvider`\n\nI hope to find a solution.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2001,2004,2005],{"name":2002,"color":2003},"bug","d73a4a",{"name":1988,"color":1989},{"name":2006,"color":2007},"triage","ffffff",3932,"Nuxt3 SSR is set to false, the tooltip and toast become invalid","2025-04-18T11:09:10Z","https://github.com/nuxt/ui/issues/3932",0.77129793,{"description":2014,"labels":2015,"number":2021,"owner":1991,"repository":1992,"state":1993,"title":2022,"updated_at":2023,"url":2024,"score":2025},"### Description\n\nAs it currently stands, the UTree does not really support lazy loading nodes (eg. via an API). Is this something that could be added? similar to this Naive UI example: https://codesandbox.io/p/sandbox/9vl592\n\n### Additional context\n\n_No response_",[2016,2019,2020],{"name":2017,"color":2018},"enhancement","a2eeef",{"name":1988,"color":1989},{"name":2006,"color":2007},3588,"UTree: request for async loading nodes","2025-03-17T10:39:50Z","https://github.com/nuxt/ui/issues/3588",0.7794275,{"description":2027,"labels":2028,"number":2033,"owner":1991,"repository":2034,"state":1993,"title":2035,"updated_at":2036,"url":2037,"score":2038},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.16.0\n- Nuxt Version: 3.13.2\n- CLI Version: 3.15.0\n- Nitro Version: 2.9.7\n- Package Manager: pnpm@9.12.1\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/test-utils/module@3.14.4\n- Build Modules: -\n\n\n### Reproduction\n\nCreate a new Nuxt projet, install test suite following [this link](https://nuxt.com/docs/getting-started/testing)\nCreate a simple test and run pnpm dev. \n\nOpen devtools and run the tests\n\n\n### Describe the bug\n\nTests run from the devtools or the Vitest UI url on `pnpm dev` are broken with `TypeError: Cannot read properties of undefined (reading 'vueApp')\n`\n\n\n\nHowever, running `vitest --ui `manually is working\n\n\n\n### Additional context\n\nThis happens even with the most basic vitest config file and nuxt config\n```typescript\nimport { fileURLToPath } from 'node:url'\nimport { defineVitestConfig } from '@nuxt/test-utils/config'\n\nexport default defineVitestConfig({\n test: {\n environment: 'nuxt',\n },\n})\n\n``` \n\n```typescript\n// https://nuxt.com/docs/api/configuration/nuxt-config\nexport default defineNuxtConfig({\n compatibilityDate: '2024-04-03',\n devtools: { enabled: true },\n modules: [\n '@nuxt/test-utils/module'\n ]\n})\n\n``` \n\nSpec file: \n```typescript\nimport { it } from 'vitest'\nimport { mountSuspended } from '@nuxt/test-utils/runtime'\nimport App from '../app.vue'\n\nit('can mount some component', async () => {\n await mountSuspended(App)\n})\n\n``` \n\nSince test are working by running `vitest --ui` it isn't blocking but it kinda defeat the whole purpose of using `@nuxt/test-utils/module`, which seemed very convenient\n\n### Logs\n\n_No response_",[2029,2030],{"name":2002,"color":2003},{"name":2031,"color":2032},"good first issue","7057ff",989,"test-utils","Testing in devtools fails","2025-02-11T15:10:14Z","https://github.com/nuxt/test-utils/issues/989",0.78414285,{"description":2040,"labels":2041,"number":2046,"owner":1991,"repository":1992,"state":1993,"title":2047,"updated_at":2048,"url":2049,"score":2050},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\nIn certain situations, it’s necessary to display a loading indicator, but not all components currently include this feature. It would be helpful to have a **composable** and **directive** for such cases.\n\n### How it should work\n\nA semi-transparent overlay should be rendered over the target, containing a loading icon.\n\n### How to use\n\n#### Composable `useLoading`\n\n```vue\n\u003Cscript setup lang=\"ts\">\nconst layout = ref\u003CHTMLDivElement | null>(null)\nconst { start, stop } = useLoading(layout)\n\nfunction startLoading() {\n start()\n setTimeout(stop, 2000)\n}\n\u003C/script>\n\n\u003Ctemplate>\n \u003Cdiv ref=\"layout\">\n ...\n \u003C/div>\n \u003CUButton @click=\"startLoading\">Show loading\u003C/UButton>\n\u003C/template>\n```\n\n#### Directive `v-loading`\n\n```vue\n\u003Cscript setup lang=\"ts\">\nconst isLoading = ref(false)\n\u003C/script>\n\n\u003Ctemplate>\n \u003Cdiv v-loading=\"isLoading\">\n ...\n \u003C/div>\n\u003C/template>\n```\n\n### Additional context\n\nHere’s how it’s implemented in other libraries:\n\n- [Element Plus - Loading](https://element-plus.org/en-US/component/loading.html) \n- [Vue Loading](https://coffcer.github.io/vue-loading/)",[2042,2045],{"name":2043,"color":2044},"feature","A27AF6",{"name":1988,"color":1989},2668,"Proposal to add a loading component","2024-11-18T12:01:05Z","https://github.com/nuxt/ui/issues/2668",0.7859445,{"description":2052,"labels":2053,"number":2057,"owner":1991,"repository":1992,"state":1993,"title":2058,"updated_at":2059,"url":2060,"score":2061},"### 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_",[2054,2055,2056],{"name":2017,"color":2018},{"name":1988,"color":1989},{"name":2006,"color":2007},3810,"[UForm] Feature Request: Make deferInputValidation Configurable in useFormField","2025-04-06T16:27:47Z","https://github.com/nuxt/ui/issues/3810",0.7877802,{"description":2063,"labels":2064,"number":2067,"owner":1991,"repository":2068,"state":2069,"title":2070,"updated_at":2071,"url":2072,"score":2073},"- [x] Move Revue contacts\n- [x] Subscribe form to contact Sendgrid API",[2065],{"name":2017,"color":2066},"1ad6ff",1104,"nuxt.com","closed","Migrate newsletter to SendGrid","2023-01-10T15:04:54Z","https://github.com/nuxt/nuxt.com/issues/1104",0.76869905,{"description":2075,"labels":2076,"number":2079,"owner":1991,"repository":2068,"state":2069,"title":2080,"updated_at":2081,"url":2082,"score":2083},"- [ ] Missing spaces for tablet sizes\n\n- [ ] Responsive lg: fix searchbar \n\n\n\n\n\n\n",[2077],{"name":2002,"color":2078},"ff281a",1054,"[Responsive] Tablet layout","2023-02-15T12:31:05Z","https://github.com/nuxt/nuxt.com/issues/1054",0.76957744,{"description":2085,"labels":2086,"number":2087,"owner":1991,"repository":2088,"state":2069,"title":2089,"updated_at":2090,"url":2091,"score":2092},"I setup the Module on newest releases and I could not bring up my font with tailwindcss.\n\nAfter seeing this discussion\nhttps://github.com/tailwindlabs/tailwindcss/discussions/13890\n\n```\n@theme {\n --font-sans: \"Nunito\", sans-serif;\n}\n```\n\nfont-sans seems the way to go and not font-display.\n\nIs that true? i am not into that. If so, we need to change the docs: https://fonts.nuxt.com/get-started/usage#v4 ",[],593,"fonts","Docs may be outdated","2025-04-11T08:37:30Z","https://github.com/nuxt/fonts/issues/593",0.77128357,{"description":2094,"labels":2095,"number":2087,"owner":1991,"repository":2068,"state":2069,"title":2097,"updated_at":2098,"url":2099,"score":2092},"Carousel should be bigger",[2096],{"name":2002,"color":2078},"[Docs] Framework v2 improve carousel","2023-02-15T12:30:49Z","https://github.com/nuxt/nuxt.com/issues/593",["Reactive",2101],{},["Set"],["ShallowReactive",2104],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"f4ws_cNmQXdQD5UYcgp9ztCGhIWTaWJufbE58h19uzI":-1},"/nuxt/ui/3814"]