\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```",[2012,2015,2016],{"name":2013,"color":2014},"bug","d73a4a",{"name":1988,"color":1989},{"name":2017,"color":2018},"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.79395366,{"description":2025,"labels":2026,"number":2030,"owner":1991,"repository":1992,"state":1993,"title":2031,"updated_at":2032,"url":2033,"score":2034},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.1.0`\n- Nuxt Version: `3.16.2`\n- CLI Version: `3.24.0`\n- Nitro Version: `2.11.8`\n- Package Manager: `yarn@4.7.0`\n- Builder: `-`\n- User Config: `modules`, `ssr`, `components`, `app`, `css`, `runtimeConfig`, `compatibilityDate`, `nitro`, `vite`, `eslint`\n- Runtime Modules: `@pinia/nuxt@0.10.1`, `pinia-plugin-persistedstate/nuxt@4.2.0`, `@nuxt/ui@3.0.2`, `dayjs-nuxt@2.1.11`, `@nuxt/eslint@1.3.0`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/sandbox/festive-feather-mzq49q\n\nIn the second select (which is wrapped in a form tag), don't select anything, and click save to submit the form.\n\nIt should show the browser \"this input is required\" tooltip.\n\n### Description\n\nI can't really understand why/how this happens. Sometimes, the `required` prop on a Select component will not prevent the form to be submitted. But sometimes it's working fine.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2027,2028,2029],{"name":2013,"color":2014},{"name":1988,"color":1989},{"name":2017,"color":2018},3882,"Select required sometimes not working","2025-04-14T08:11:48Z","https://github.com/nuxt/ui/issues/3882",0.7963777,{"description":2036,"labels":2037,"number":2038,"owner":1991,"repository":2039,"state":2040,"title":2041,"updated_at":2042,"url":2043,"score":2044}," field module resolution of the package at C:\\Users\\colli\\OneDrive\\Desktop\\uppr_v1\\node_modules\\@iconify\\utils\\package.json imported from C:\\Users\\colli\\OneDrive\\Desktop\\uppr_v1\\node_modules. Mapping specifiers ending in \"/\" is no longer supported. (Use `node --trace-deprecation ...` to show where the warning was created) - I am getting this error when running nuxt buid",[],287,"icon","closed","(node:17640) [DEP0155] DeprecationWarning: Use of deprecated trailing slash pattern mapping \"./\" in the \"exports\"","2024-10-28T13:31:06Z","https://github.com/nuxt/icon/issues/287",0.6935897,{"labels":2046,"number":2053,"owner":1991,"repository":1991,"state":2040,"title":2054,"updated_at":2055,"url":2056,"score":2057},[2047,2049,2050],{"name":2048,"color":2018},"stale",{"name":2002,"color":2003},{"name":2051,"color":2052},"2.x","d4c5f9",6655,"IOS Splash screens not working","2023-01-22T15:34:46Z","https://github.com/nuxt/nuxt/issues/6655",0.7144609,{"description":2059,"labels":2060,"number":2065,"owner":1991,"repository":1992,"state":2040,"title":2066,"updated_at":2067,"url":2068,"score":2069},"### Description\n\nsame as https://ui.nuxt.com/getting-started/installation#edge and https://ui.nuxt.com/pro/getting-started/installation#edge to test new components before release \n\n### Additional context\n\n_No response_",[2061,2064],{"name":2062,"color":2063},"enhancement","a2eeef",{"name":1988,"color":1989},2962,"Create a edge version for `@nuxt/ui` and `@nuxt/ui-pro` v3","2025-01-25T13:12:16Z","https://github.com/nuxt/ui/issues/2962",0.74390095,{"description":2071,"labels":2072,"number":2075,"owner":1991,"repository":2076,"state":2040,"title":2077,"updated_at":2078,"url":2079,"score":2080},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.11.2\r\n- CLI Version: 3.11.1\r\n- Nitro Version: 2.9.6\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-xdspn8\n\n### Describe the bug\n\nIt is impossible to test server API and server route implementations directly, because vitest does not auto import nitro (h3) functions like e.g. `defineEventHandler()`.\r\n\r\nWhen executing the test in the linked minimal reproduction, I receive this error:\r\n\r\n```\r\nFAIL test/server/routes/something.spec.ts [ test/server/routes/something.spec.ts ]\r\nReferenceError: defineEventHandler is not defined\r\n ❯ eval server/routes/something.ts:1:217\r\n ❯ eval test/server/routes/something.spec.ts:2:31\r\n```\n\n### Additional context\n\nserver/routes/something.ts\r\n```typescript\r\nexport default defineEventHandler(() => 'OK');\r\n```\r\n\r\ntest/routes/something.spec.ts\r\n```typescript\r\nimport { it } from 'vitest';\r\nimport handler from '../../../server/routes/something';\r\n\r\nit('should return OK', () => {\r\n const response = handler({} as any);\r\n expect(response).toBe('OK');\r\n});\r\n\r\n```\n\n### Logs\n\n_No response_",[2073],{"name":2002,"color":2074},"5D08F5",827,"test-utils","vitest does not resolve nitro (h3) auto-imports","2024-04-24T10:39:40Z","https://github.com/nuxt/test-utils/issues/827",0.7627821,{"description":2082,"labels":2083,"number":2084,"owner":1991,"repository":2085,"state":2040,"title":2086,"updated_at":2087,"url":2088,"score":2089},"### 📚 Description\r\n\r\nI got a 404 error when I accessed the **learn more** link on the [cloudflare](https://nuxt.com/deploy/cloudflare) page.\r\nI investigated the cause and found that the URL path was incorrect.",[],1520,"nuxt.com","bug: wrong link to Zero-Config Providers","2024-03-03T08:40:08Z","https://github.com/nuxt/nuxt.com/issues/1520",0.7724779,{"description":2091,"labels":2092,"number":1079,"owner":1991,"repository":2093,"state":2040,"title":2094,"updated_at":2095,"url":2096,"score":2097},"this is a tracker issue for migrating from existing nuxt font solutions to `@nuxt/fonts` (and thereby discovering issues with it, hopefully!)\r\n\r\n```[tasklist]\r\n### Tasks\r\n- [ ] https://github.com/danielroe/roe.dev/pull/1376\r\n- [ ] https://github.com/nuxt/nuxt.com/pull/1510\r\n``` ",[],"fonts","testing out `@nuxt/fonts`","2024-02-28T14:08:04Z","https://github.com/nuxt/fonts/issues/7",0.7778764,["Reactive",2099],{},["Set"],["ShallowReactive",2102],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"zlu1zfwUrBukS79ViMFlEJjmlosj9-lYhAMHhocuKuo":-1},"/nuxt/test-utils/842"]