\n\u003C/template>\n```\n\nThis is working when loading the page SSR, but navigating to the page results in errors like this:\n`DR5f3n0Z.js:52 [Icon] failed to load icon 'twemoji:flag-hungary'`\n\nHow can I create the icon names dynamically?",[3026],{"name":3027,"color":3028},"need-repro","A50BA3",321,"nuxt","icon","open","Dynamic icon name","2024-12-12T08:54:20Z","https://github.com/nuxt/icon/issues/321",0.7665595,{"description":3038,"labels":3039,"number":3046,"owner":3030,"repository":3030,"state":3032,"title":3047,"updated_at":3048,"url":3049,"score":3050},"### Describe the feature\r\n\r\nI'm reaching out with a suggestion that might enhance the documentation, particularly for those looking to disable code splitting. We recently came across a method to inline dynamic imports through the Rollup configuration, effectively disabling code splitting. This was discovered in a ViteJS discussion ([Reference here](https://github.com/vitejs/vite/discussions/13925#discussioncomment-7709077)):\r\n\r\n```typescript\r\nbuild: {\r\n rollupOptions: {\r\n output: {\r\n inlineDynamicImports: true\r\n }\r\n }\r\n}\r\n```\r\n\r\nComing forth to this solution took us a considerable amount of time. A search in the Nuxt documentation for \"code splitting\" yielded few results. Including this information in the Nuxt documentation could significantly improve the developer experience, making this knowledge more readily accessible.\r\n\r\nThere are practical scenarios, such as ensuring seamless access for mobile users with unstable internet connections, where disabling code splitting can be beneficial. Although code splitting with dynamic imports provides some fantastic optimizations, ensuring that the entire page content is downloaded and ready on the first load can be crucial in these situations. I do understand, that there are [ways to handle these errors](https://nuxt.com/docs/getting-started/error-handling#errors-with-js-chunks), but unfortunately, as the application grows, it just creates too much room for error.\r\n\r\nI must admit my understanding of the implications of setting `inlineDynamicImports` to `true` is not comprehensive. One of our applications, deployed as a static single-page app, benefits from this setting, but I'm uncertain about its effects in other build configurations. I would greatly appreciate if someone could provide further insight on this.\r\n\r\nAdditionally, I would like your opinion on the best section within the Nuxt documentation to include this information, ensuring it's easily found by those who need it.\r\n\r\nLooking forward to your thoughts and guidance on this matter.\r\n\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3040,3043],{"name":3041,"color":3042},"documentation","5319e7",{"name":3044,"color":3045},"discussion","538de2",24539,"Docs: Suggestion for documenting disabling code splitting","2024-06-30T11:06:44Z","https://github.com/nuxt/nuxt/issues/24539",0.76809484,{"description":3052,"labels":3053,"number":3057,"owner":3030,"repository":3058,"state":3059,"title":3060,"updated_at":3061,"url":3062,"score":3063},"### Environment\r\n\r\n```\r\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v21.6.1\r\n- Nuxt Version: 3.13.1\r\n- CLI Version: 3.13.1\r\n- Nitro Version: 2.9.7\r\n- Package Manager: bun@1.1.26\r\n- Builder: -\r\n- User Config: compatibilityDate, devtools, modules\r\n- Runtime Modules: @nuxt/ui@2.18.4\r\n- Build Modules: -\r\n------------------------------\r\n```\r\n\r\n### Version\r\n\r\n2.18.4\r\n\r\n### Reproduction\r\n\r\nhttps://github.com/MickL/nuxtui-colors-bug\r\n\r\n### Description\r\n\r\nWhen the color prop is created dynamically, some css styles are not generated, especially for subtle and soft variants:\r\n\r\nFor example, `subtle` badges dont have correct border color and the background colors are missing:\r\n\r\n\u003Cimg width=\"237\" alt=\"Bildschirmfoto 2024-09-14 um 18 47 17\" src=\"https://github.com/user-attachments/assets/a3dd5d73-02ae-43d5-96ff-3ef67342cb1d\">\r\n\r\nIt should look like this:\r\n\r\n\u003Cimg width=\"236\" alt=\"Bildschirmfoto 2024-09-14 um 18 46 37\" src=\"https://github.com/user-attachments/assets/7fd2bd00-f2c2-40ed-a7f8-23ec07266d29\">\r\n\r\nIn my reproduction repo I used a table:\r\n```\r\n \u003CUTable :columns :rows>\r\n \u003Ctemplate #colors-data=\"{row}\">\r\n \u003CUBadge :color=\"row.color\" variant=\"subtle\">Subtle Badge\u003C/UBadge>\r\n \u003CUButton :color=\"row.color\" variant=\"soft\">Soft Button\u003C/UButton>\r\n \u003C/template>\r\n \u003C/UTable>\r\n```",[3054],{"name":3055,"color":3056},"bug","d73a4a",2199,"ui","closed","Missing tailwind classes for dynamic colors","2024-09-23T10:31:05Z","https://github.com/nuxt/ui/issues/2199",0.68194044,{"description":3065,"labels":3066,"number":3067,"owner":3030,"repository":3068,"state":3059,"title":3069,"updated_at":3070,"url":3071,"score":3072},"[nuxi build](https://nuxt.com/docs/api/commands/build) is missing the docs for `--preset`\r\n\r\nSource: https://github.com/nuxt/cli/blob/main/src/commands/build.ts#L22",[],1556,"nuxt.com","docs: nuxi build missing `--preset` option","2024-04-12T22:06:13Z","https://github.com/nuxt/nuxt.com/issues/1556",0.7202302,{"description":3074,"labels":3075,"number":3084,"owner":3030,"repository":3058,"state":3059,"title":3085,"updated_at":3086,"url":3087,"score":3088},"### Description\n\n**Feature Request: Add \"Copy Page as Markdown\" Button to Nuxt UI v3 Documentation**\n\n**Description:**\nAdd a button to each component documentation page that allows users to copy the current page content in markdown format.\n\n**Problem:**\n- The full documentation text at ui.nuxt.com/llms-full.txt contains too much information when I only need documentation for specific components\n- GitHub raw files don't show the dynamic content visible on the actual documentation site\n- Need an easy way to copy specific component documentation for use in prompts to AI assistants\n\n**Proposed Solution:**\nAdd a \"Copy Page as Markdown\" button to each documentation page, similar to the implementation on https://modelcontextprotocol.io/introduction\n\n**User Benefit:**\nThis feature would let users easily copy specific component documentation to paste as additional context in AI prompts, improving the relevance and focus of AI assistance for Nuxt UI development.\n\n\n\n### Additional context\n\n_No response_",[3076,3078,3081],{"name":3041,"color":3077},"0075ca",{"name":3079,"color":3080},"enhancement","a2eeef",{"name":3082,"color":3083},"v3","49DCB8",3923,"Docs: Add \"Copy Page as Markdown\" Button to Nuxt UI v3 Documentation","2025-06-24T10:11:25Z","https://github.com/nuxt/ui/issues/3923",0.7337409,{"description":3090,"labels":3091,"number":3093,"owner":3030,"repository":3058,"state":3059,"title":3094,"updated_at":3095,"url":3096,"score":3097},"### Description\n\nWhen using a Table component, it would be a cool feature to allow the items to be modified in place and an event emitted. There arent really many good solutions for this in Vue ecosystem, that I know of. \n\n### Additional context\n\n_No response_",[3092],{"name":3079,"color":3080},2168,"Make an inplace editable table","2024-09-11T14:14:15Z","https://github.com/nuxt/ui/issues/2168",0.7408877,{"description":3099,"labels":3100,"number":3103,"owner":3030,"repository":3058,"state":3059,"title":3104,"updated_at":3105,"url":3106,"score":3107},"### Description\n\nAs it is today, when you change the neutral color on dark mode, the whole background changes, which I personally love.\n\nI think it would be nice if that happened on light mode as well. So instead of using #fff, using neutral-50.\n\nWould that make sense?\n\nI'm willing to contribute if this suggestion is accepted.\n\n### Additional context\n\n_No response_",[3101,3102],{"name":3079,"color":3080},{"name":3082,"color":3083},3189,"Change light-mode body bg-color from white to neutral-50","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3189",0.74583256,{"description":3109,"labels":3110,"number":3114,"owner":3030,"repository":3030,"state":3059,"title":3115,"updated_at":3116,"url":3117,"score":3118},"\r\nthere is my config\r\n```javascript\r\nimport path from 'path'\r\nimport CopyWebpackPlugin from 'copy-webpack-plugin'\r\n\r\nexport default {\r\nbuild: {\r\n extend(config, ctx) {\r\n config.plugins.push(\r\n new CopyWebpackPlugin([\r\n {\r\n from: 'node_modules/mavon-editor/dist/highlightjs',\r\n to: path.join(__dirname, 'static/plugins/highlightjs/')\r\n }\r\n ])\r\n )\r\n\r\n return config\r\n }\r\n }\r\n}\r\n\r\n```\r\n\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c9883\">#c9883\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3111],{"name":3112,"color":3113},"2.x","d4c5f9",6538,"Copy-Webpack-Plugin can not work?","2023-01-18T21:49:16Z","https://github.com/nuxt/nuxt/issues/6538",0.7529289,{"description":3120,"labels":3121,"number":3127,"owner":3030,"repository":3068,"state":3059,"title":3128,"updated_at":3129,"url":3130,"score":3131},"On sub-pages (paths longer than 1 level) 404 is not triggered\n\nEx:\n\nhttps://nuxt.com/unknown => Triggers 404\nhttps://nuxt.com/modules/unknown => Broken page",[3122,3124],{"name":3055,"color":3123},"ff281a",{"name":3125,"color":3126},"SEO","01403D",1046,"404s handling","2023-06-06T12:14:30Z","https://github.com/nuxt/nuxt.com/issues/1046",0.7609995,{"description":3133,"labels":3134,"number":3136,"owner":3030,"repository":3058,"state":3059,"title":3137,"updated_at":3138,"url":3139,"score":3140},"### Description\n\nWould be nice to have the option to preserve theme per component, for example if you have dark footer and it needs to be dark in both themes, then any component residing inside it will change the colours, but in such a case you might want to preserve dark theme for components in dark footer. \r\n\r\nYes it's possible to overwrite styles per component, but for some use cases this could become quite a clutter.\r\nAlso this option could nicely work with \"hybrid\" themes.\n\n### Additional context\n\n_No response_",[3135],{"name":3079,"color":3080},2087,"Preserve theme for component","2024-09-06T10:16:43Z","https://github.com/nuxt/ui/issues/2087",0.76200175,["Reactive",3142],{},["Set"],["ShallowReactive",3145],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f8x2wEsWNn3TH1QxGCXz2c0zlLJxklFwJypW5fuhyGSo":-1},"/nuxt/ui/2828"]