",[2006,2008,2011],{"name":1985,"color":2007},"a2eeef",{"name":2009,"color":2010},"v3","49DCB8",{"name":2012,"color":2013},"triage","ffffff",3270,"ui","[Feature request] Toast hide progress in app.config","2025-02-09T17:11:11Z","https://github.com/nuxt/ui/issues/3270",0.72157675,{"description":2021,"labels":2022,"number":2028,"owner":1988,"repository":1988,"state":1990,"title":2029,"updated_at":2030,"url":2031,"score":2032},"### Describe the feature\n\nAdds a [`Link`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Link) header from the renderer to give the browser hints in the `HTTP 200` response of additional resources while downloading / parsing the server response payload. The intention is to decrease page load time by allowing the browser to simultaneously request upcoming resources needed by the DOM before they are identified. \n\nIf the browser or any proxies don't support [`HTTP 103`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/103) Early Hints, then including hints in the later `HTTP 200` still provides early notice. Implementing the feature should hopefully be of minimal operating disruption compared to adopting `HTTP 103` while providing some of the benefits.\n\nAnecdotal evidence suggests that unloaded CSS files are blocking the client side loading of pages until fetched as a subsequent resource in Lighthouse testing. Hints may reduce page load time by reducing the gap between the resource identified and render awaiting resource including JS and CSS.\n\nFeedback and suggestions are welcome!\n\n---\n\n### Example of how it could initially work:\nhttps://github.com/nuxt/nuxt/compare/main...IO-Fire:nuxt:feature/write-link-header\nAlthough this implementation appears to only show JS and not styles (test sample size of 1). This may also impact the current `103` early hints feature.\n\n#### SSG Support\nUpdate the route rules' headers for each page before the creating completing the route rendering.\nOR\nMay require changes in the Nitro static presets to encompass the headers being identified at render time rather than at route creation. \n\n##### Header rule limits\nSome hosting providers including Cloudflare Pages have limits on headers.\n\nCloudflare Pages limits the total number of \"header rules\" similar to route rules. \n\n100 pages / routes with headers would use 100 headers rules. This may limit the number of pages within a site without workarounds such as https://github.com/nuxt-modules/security/issues/504#issuecomment-2562018536\n\n### Module Implementation\nModule implementation may not be possible as access to the render's data may not be exposed to a module.\n\n### Additional information\n\n- [x] Would you be willing to help implement this feature?\n- [x] Could this feature be implemented as a module?\n\n### Final checks\n\n- [x] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [x] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2023,2025],{"name":1985,"color":2024},"8DEF37",{"name":2026,"color":2027},"discussion","538de2",30758,"ResourceHints `Link` header in `HTTP 200`","2025-02-03T21:02:39Z","https://github.com/nuxt/nuxt/issues/30758",0.7284751,{"description":2034,"labels":2035,"number":2038,"owner":1988,"repository":2015,"state":2039,"title":2040,"updated_at":2041,"url":2042,"score":2043},"### Description\n\nHey!\n\nIt would be nice to have the primary/secondary/neutral/etc colours defined in `app.config.ts` directly as tailwind variables (ex: text-primary-500)\n\nRight now we have to define the colours both in `app.config.ts` and `tailwind.config.js` to be able to do that. (the new `main.css` would require to create a variable for each sub-colour manually so not worth using it) \n\nFor `neutral`, since it's a tailwind colour, it could be named `text-neutr-500`\nOr maybe name all colours with something like `text-Uneutral-500`\n\n\n### Additional context\n\n_No response_",[2036,2037],{"name":1985,"color":2007},{"name":2009,"color":2010},2948,"closed","Add theme colors as tailwind variables","2025-02-06T16:29:04Z","https://github.com/nuxt/ui/issues/2948",0.6882235,{"description":2045,"labels":2046,"number":2050,"owner":1988,"repository":2015,"state":2039,"title":2051,"updated_at":2052,"url":2053,"score":2054},"### Description\n\nHello, \n\nI was looking for adding Català language to nuxt ui v3. However, i am not used to pull requests but also, the 'ca' code may be confusing with Canada one (and may be others?)\n\nCan someone help me on that way so I will be able to use the locale in the UApp componente :) ?\n\nThank you very much ! \n\n```\n\nimport { defineLocale } from '../composables/defineLocale'\n\nexport default defineLocale({\n name: 'Català',\n code: 'ca',\n messages: {\n inputMenu: {\n noMatch: 'No hi ha dades coincidents',\n noData: 'Sense dades',\n create: 'Crear \"{label}\"'\n },\n calendar: {\n prevYear: 'Any anterior',\n nextYear: 'Any següent',\n prevMonth: 'Mes anterior',\n nextMonth: 'Mes següent'\n },\n inputNumber: {\n increment: 'Incrementar',\n decrement: 'Decrementar'\n },\n commandPalette: {\n placeholder: 'Escriu una ordre o cerca...',\n noMatch: 'No hi ha dades coincidents',\n noData: 'Sense dades',\n close: 'Tancar'\n },\n selectMenu: {\n noMatch: 'No hi ha dades coincidents',\n noData: 'Sense dades',\n create: 'Crear \"{label}\"',\n search: 'Cerca...'\n },\n toast: {\n close: 'Tancar'\n },\n carousel: {\n prev: 'Anterior',\n next: 'Següent',\n goto: 'Anar a la diapositiva {slide}'\n },\n modal: {\n close: 'Tancar'\n },\n slideover: {\n close: 'Tancar'\n },\n alert: {\n close: 'Tancar'\n },\n table: {\n noData: 'Sense dades'\n }\n }\n})\n\n```\n\n### Additional context\n\n_No response_",[2047,2048,2049],{"name":1985,"color":2007},{"name":2009,"color":2010},{"name":2012,"color":2013},3477,"Adding Català language","2025-03-20T14:09:46Z","https://github.com/nuxt/ui/issues/3477",0.7052939,{"description":2056,"labels":2057,"number":2058,"owner":1988,"repository":2059,"state":2039,"title":2060,"updated_at":2061,"url":2062,"score":2063},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.14.0`\n- Nuxt Version: `3.16.0`\n- CLI Version: `3.22.5`\n- Nitro Version: `2.11.5`\n- Package Manager: `bun@1.2.4`\n- Builder: `-`\n- User Config: `runtimeConfig`, `modules`, `app`, `site`, `sitemap`, `robots`, `css`, `icon`, `image`, `ui`, `devtools`, `future`, `unhead`, `compatibilityDate`\n- Runtime Modules: `@nuxt/ui@3.0.0-beta.3`, `@pinia/nuxt@0.10.1`, `@nuxt/scripts@0.10.5`, `@nuxt/image@1.9.0`, `@nuxtjs/seo@2.2.0`\n- Build Modules: `-`\n\n### Reproduction\n\nnda\n\n### Describe the bug\n\nnr dev\n$ nuxt dev\nNuxt 3.16.0 with Nitro 2.11.5 nuxi 8:23:08 PM\n 8:23:08 PM\n ➜ Local: http://localhost:3003/\n ➜ Network: use --host to expose\n\n ➜ DevTools: press Shift + Option + D in the browser (v2.2.1) 8:23:10 PM\n\n\n✔ Nuxt Icon loaded local collection elfi with 70 icons 8:23:10 PM\nℹ Running with compatibility version 4 nuxt 8:23:10 PM\n✔ Vite client built in 190ms 8:23:11 PM\n✔ Vite server built in 528ms 8:23:12 PM\n\n[nitro 8:23:14 PM] ERROR Error: Could not load /\u003Cmy-path>/node_modules/unenv/dist/runtime/runtime/mock/empty.mjs (imported by node_modules/nuxt-og-image/dist/runtime/server/og-image/satori/instances.js): ENOENT: no such file or directory, open '/\u003Cmy-path>/node_modules/unenv/dist/runtime/runtime/mock/empty.mjs'\n\n\nundefined\n\n### Additional context\n\nUpgraded by \"nuxi upgrade -f\" from 3.15.4 and couldn't able to start properly with provided error.\nTried with unhead flag in nuxt.config - same error\n```\nunhead: {\n legacy: true,\n }\n```\n\n### Logs\n\n```shell-script\n\n```",[],414,"scripts","Nuxt 3.16.0 won't start properly nor dev nor build","2025-03-07T18:58:03Z","https://github.com/nuxt/scripts/issues/414",0.70843714,{"description":2065,"labels":2066,"number":2071,"owner":1988,"repository":2015,"state":2039,"title":2072,"updated_at":2073,"url":2074,"score":2075},"### Description\n\nHello, we are currently a small team using nuxt UI pro version 2. We've seen that the new Nuxt UI 3 version is in alpha and we'd like to know if a stable release is planned soon?\n\nWe've seen that Nuxt UI 3 is going to take a long time to migrate and we'd like to start work quickly. Do you think it's cost-effective to make the switch now, or is it better to wait for a more stable version?\n\nThanks for reading ^^",[2067,2070],{"name":2068,"color":2069},"question","d876e3",{"name":2009,"color":2010},3371,"Nuxt UI V3 official release date","2025-02-21T09:22:07Z","https://github.com/nuxt/ui/issues/3371",0.7150928,{"description":2077,"labels":2078,"number":2084,"owner":1988,"repository":2015,"state":2039,"title":2085,"updated_at":2086,"url":2087,"score":2088},"### Description\n\nI really love all the work that went into this, but it's currently connected to vue-router for `Link` and `Pagination` components. I would love to see these become optional dependencies so it can be used with projects that do not use `vue-router`.\n\nMaybe there is some way to stub out the link components to enable support for Inertia \\ default HTML?",[2079,2080,2081],{"name":2068,"color":2069},{"name":2009,"color":2010},{"name":2082,"color":2083},"vue","42b883",3001,"How likely is it that we'll see a routerless version?","2025-04-14T08:47:28Z","https://github.com/nuxt/ui/issues/3001",0.7163633,{"description":2090,"labels":2091,"number":2098,"owner":1988,"repository":2015,"state":2039,"title":2099,"updated_at":2100,"url":2101,"score":2102},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.10.0\n- Nuxt Version: 3.13.2\n- CLI Version: 3.14.0\n- Nitro Version: 2.9.7\n- Package Manager: pnpm@9.12.1\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Version\n\nv2.18.7\n\n### Reproduction\n\n-\n\n### Description\n\nThis outputs two unnecessary `::` at the end. Looks like something is going wrong with the collapsible. Also when I add other fields after the collapsible, it breaks as well.\n\n```markdown\n::field-group\n::field{name=\"fallback_image\" type=\"string\"}\n::collapsible{name=\"options\"}\n\ntest\n\n::\n::\n::\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2092,2095],{"name":2093,"color":2094},"bug","d73a4a",{"name":2096,"color":2097},"pro","5BD3CB",2426,"Weird collapsible formatting in field-group","2024-11-19T15:20:24Z","https://github.com/nuxt/ui/issues/2426",0.73159266,["Reactive",2104],{},["Set"],["ShallowReactive",2107],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"BOEwRB6-Ee0oXdTPt6Kx3CaP7B6UaZXEjMSq8p16qDg":-1},"/nuxt/ui/3208"]