\n```\n\nThere are lots of instances where a button need to be smaller on mobile, so would be nice to have that! I didn't found anything in the docs\n\nP.S. bought Nuxt UI Pro a couple of days ago to support the team. Keep up the great work! 😄",[2903,2906],{"name":2904,"color":2905},"question","d876e3",{"name":2907,"color":2908},"stale","ededed",2390,"nuxt","ui","open","Buttons size based on device?","2025-02-14T01:58:50Z","https://github.com/nuxt/ui/issues/2390",0.7771544,{"description":2918,"labels":2919,"number":2923,"owner":2910,"repository":2924,"state":2912,"title":2925,"updated_at":2926,"url":2927,"score":2928},"### 📚 Is your documentation request related to a problem?\n\n📚 Is your documentation request related to a problem?\n\nI couldn't find in the docs how to display in the devtools so that I can know which one is which.\n\n```ts\n useScript(\n {\n src: \"xxx\",\n id: \"super-script-src\",\n },\n {\n devtools: {\n registryKey: \"SuperScript\", // Key used to map to the registry script for Nuxt DevTools. as per JS Docs ( It's not the name \n registryMeta: {\n name: \"SuperScript\", // We can include here for example the name\n },\n },\n },\n );\n```\n\nExample after I included that meta data in the devtools\n\n\n\n\n\n### 🔍 Where should you find it?\n\nI would say a tab with devtools in the sidebar with this and more information on how useful the devtools is, would be really important\n\n### ℹ️ Additional context\n\n_No response_",[2920],{"name":2921,"color":2922},"documentation","0075ca",332,"scripts","How to display in the devtools name of the scripts","2024-12-06T09:14:08Z","https://github.com/nuxt/scripts/issues/332",0.7929104,{"description":2930,"labels":2931,"number":2935,"owner":2910,"repository":2910,"state":2936,"title":2937,"updated_at":2938,"url":2939,"score":2940},"Hello,\r\n\r\nI use [markdown-it](https://github.com/nuxt-community/modules/tree/master/packages/markdownit) module to parse `.md` files, with this component to convert internal links :\r\n\r\n```html\r\n\u003Ctemplate>\r\n \u003Cdiv v-html=\"content\">\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript>\r\nexport default {\r\n props: ['content'],\r\n mounted() {\r\n this.addListeners()\r\n },\r\n beforeDestroy() {\r\n this.removeListeners()\r\n },\r\n watch: {\r\n 'content': 'contentUpdated'\r\n },\r\n methods: {\r\n navigate(event) {\r\n const href = event.target.getAttribute('href')\r\n if (href && href[0] === '/') {\r\n event.preventDefault()\r\n this.$router.push(href)\r\n }\r\n },\r\n contentUpdated() {\r\n this.removeListeners()\r\n this.$nextTick(() => {\r\n this.addListeners()\r\n })\r\n },\r\n addListeners() {\r\n this._links = this.$el.getElementsByTagName('a')\r\n for (let i = 0; i \u003C this._links.length; i++) {\r\n this._links[i].addEventListener('click', this.navigate, false)\r\n }\r\n },\r\n removeListeners() {\r\n for (let i = 0; i \u003C this._links.length; i++) {\r\n this._links[i].removeEventListener('click', this.navigate, false)\r\n }\r\n this._links = []\r\n }\r\n }\r\n}\r\n\u003C/script>\r\n```\r\n\r\nIt works fine but the content of the `.md` is not html rendered with `nuxt generate`, but instead stored in the js...\r\n\r\nAny idea?\r\n\r\nThanks!\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c2488\">#c2488\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2932],{"name":2933,"color":2934},"2.x","d4c5f9",2864,"closed","Content not rendered","2023-01-18T16:09:43Z","https://github.com/nuxt/nuxt/issues/2864",0.7094805,{"description":2942,"labels":2943,"number":2952,"owner":2910,"repository":2911,"state":2936,"title":2953,"updated_at":2954,"url":2955,"score":2956},"### Description\n\nI would like to propose adding native Infinity Scrolling support to the USelectMenu component and much more for efficiently handling and displaying large datasets.\n\nCurrently, I have implemented a workaround by using a combination of a MutationObserver and dynamic class binding to detect when the dropdown menu is rendered. Once the menu is detected, I attach an onScroll event listener to implement custom infinity scrolling. Below is an example of how this has been achieved:\n\n```\n\u003Ctemplate>\n \u003CUSelectMenu :ui-menu=\"{ strategy: 'merge', base: `scroller-${randomHash}` }\" />\n\u003C/template>\n```\n\n```\n\u003Cscript setup lang=\"ts\">\nconst randomHash = Math.random().toString(36).substring(7);\n\nonMounted(() => {\n const observer = new MutationObserver((mutationsList) => {\n for (const mutation of mutationsList) {\n if (mutation.type === \"childList\") {\n const element = document.querySelector(`.scroller-${randomHash}`);\n if (element) {\n // Element has been found, add an onScroll event listener\n observer.disconnect();\n break;\n }\n }\n }\n });\n\n observer.observe(document.body, {\n childList: true,\n subtree: true, \n });\n\n onBeforeUnmount(() => {\n observer.disconnect();\n });\n});\n\u003Cscript/>\n```\n\n### Additional context\n\n_No response_",[2944,2947,2950],{"name":2945,"color":2946},"enhancement","a2eeef",{"name":2948,"color":2949},"wontfix-v2","ffffff",{"name":2951,"color":2949},"triage",3072,"Add Infinity Scrolling Support to USelectMenu and much more components for Handling Large Datasets","2025-04-02T15:17:48Z","https://github.com/nuxt/ui/issues/3072",0.7466809,{"description":2958,"labels":2959,"number":2968,"owner":2910,"repository":2910,"state":2936,"title":2969,"updated_at":2970,"url":2971,"score":2972},"### Environment\n\nChromium Engine Version 107.0.5304.110\n\n### Reproduction\n\nhttps://nuxt.com/docs/getting-started/seo-meta\n\n### Describe the bug\n\nMarkdown render code block badly. Missing colon and question mark.\r\n\r\n\u003Cimg width=\"887\" alt=\"image\" src=\"https://user-images.githubusercontent.com/41265413/202634530-be61a161-227c-4f7a-8f4a-b7e1fd616c5e.png\">\r\n\u003Cimg width=\"448\" alt=\"image\" src=\"https://user-images.githubusercontent.com/41265413/202634544-14f76ad0-990b-40c3-a648-cb2e19a29bd0.png\">\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2960,2962,2965],{"name":2921,"color":2961},"5319e7",{"name":2963,"color":2964},"3.x","29bc7f",{"name":2966,"color":2967},"pending triage","E99695",15530,"[docs] markdown render code block badly","2023-01-19T17:53:18Z","https://github.com/nuxt/nuxt/issues/15530",0.74845225,{"description":2974,"labels":2975,"number":2981,"owner":2910,"repository":2982,"state":2936,"title":2983,"updated_at":2984,"url":2985,"score":2986},"### Environment\r\n\r\nN/A\r\n\r\n### Reproduction\r\n\r\nN/A\r\n\r\n### Describe the bug\r\n\r\nsetup fails\r\n\r\n### Additional context\r\n\r\ncc: @tobiasdiez \r\n\r\nHere are the lines\r\n\r\nhttps://github.com/nuxt/test-utils/blob/86d09da23a2d7ba6b0f3dcf2e9ca8c21655a5218/src/core/server.ts#L17-L71\r\n\r\noffending line for me was 57, but could easily be any other lines\r\n\r\nhttps://github.com/nuxt/test-utils/commit/c4df41db447afe6101df10fbe763b198b12da86d\r\n\r\nis the offending commit \r\n\r\nspecifically this change\r\n\r\nhttps://github.com/nuxt/test-utils/commit/c4df41db447afe6101df10fbe763b198b12da86d#diff-84e9c1e393b43cee97ce99909a2db3a09bf9a2435daa2066b01a838e206edec3\r\n\r\n### Logs\r\n\r\n```shell-script\r\nN/A\r\n```\r\n",[2976,2979],{"name":2977,"color":2978},"bug","d73a4a",{"name":2966,"color":2980},"5D08F5",918,"test-utils","`ctx.nuxt` does not exist when `build: false` in setup","2024-12-05T14:26:41Z","https://github.com/nuxt/test-utils/issues/918",0.76296365,{"description":2988,"labels":2989,"number":2995,"owner":2910,"repository":2911,"state":2936,"title":2996,"updated_at":2997,"url":2998,"score":2999},"### Environment\n\nnone\n\n### Version\n\nlatest\n\n### Reproduction\n\nhttps://ui.nuxt.com/pro/components/color-mode-image (example)\n\n### Description\n\nhttps://unsplash.com/documentation/changelog#unsplash-source-being-deprecated\r\n\r\nUnsplash Source is deprecated\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2990,2991,2992],{"name":2977,"color":2978},{"name":2921,"color":2922},{"name":2993,"color":2994},"pro","5BD3CB",2240,"docs: image sources from Unsplash Source not working (deprecated) ","2024-10-02T14:22:24Z","https://github.com/nuxt/ui/issues/2240",0.76609063,{"description":3001,"labels":3002,"number":2909,"owner":2910,"repository":2910,"state":2936,"title":3004,"updated_at":3005,"url":3006,"score":2916},"I am using Nuxt with Express. \r\n\r\nOut of the box, pages are translated to routes to the main domain. \r\n\r\nI am trying to use express-subdomain so that I can have some views (ex: pages/blog/**) rendered under blog.domain.com as well as domain.com/blog.\r\n\r\nWhile other files (other than pages/blog/**) continue to be available under the domain.com only. \n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c2076\">#c2076\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3003],{"name":2933,"color":2934},"How to make a specific page rendered for a subdomain when using with express?","2023-01-18T15:55:11Z","https://github.com/nuxt/nuxt/issues/2390",{"description":3008,"labels":3009,"number":3011,"owner":2910,"repository":2910,"state":2936,"title":3012,"updated_at":3013,"url":3014,"score":3015},"I've been grappling with implementing custom routing in a Nuxt3 project for the past three weeks without success. The current website is built on WordPress and features dynamic URLs such as:\n/parent-page-slug (10 pages)\n/traing-page-slug (6)\n/article-slug (200+)\n/testimonial-slug (50+)\n\nEach URL corresponds to a unique page design and will be managed using @nuxt/content. Preserving the existing URL structure is crucial to maintain our current SEO rankings and backlinks.\n\nProposed Solution:\nOne approach I'm considering is placing all Markdown files in the content directory without subfolders and creating a [...slug].vue file in the pages directory. This file would conditionally render components based on a type variable defined in the front matter of each Markdown file.\n\nDirectory Structure:\n-| content/\n---| parent-one.md\n---| training-hello.md\n---| article-1.md\n---| testimonial-1.md\n\n[...slug].vue:\n```\n\u003Ctemplate>\n \u003CParentPage v-if=\"page.type==='parent'\"/>\n \u003CTrainingPage v-if=\"page.type==='training'\"/>\n \u003CArticlePage v-if=\"page.type==='article'\"/>\n \u003CTestimonialPage v-if=\"page.type==='testimonial'\"/>\n\u003C/template>\n```\n\nAlternative Consideration:\nAlternatively, I'd prefer organizing the Markdown files into subdirectories within the content folder, such as parent, training, articles, and testimonials, while retaining the existing URL structure. This would result in URLs like /one, /running, /dog, /john\n\nDirectory Structure:\n-| content/\n---| parent\n-----| one.md\n---| training\n-----| running.md\n---| articles\n-----| dog.md\n---| testimonials\n-----| john.md\n\nChallenge:\nThe main challenge is defining custom routes that map these organized Markdown files to the desired flat URL structure without altering the existing URLs. I'm seeking guidance on how to achieve this in Nuxt3 and nuxt/content3\n\nThe slugs will be unique so if we have one in parent then we will not have it in other folders\n\nAny suggestions would be appreciated\n\nThank you",[3010],{"name":2966,"color":2967},31426,"pre-render all routes from content directory","2025-03-25T19:17:55Z","https://github.com/nuxt/nuxt/issues/31426",0.7796871,{"description":3017,"labels":3018,"number":3024,"owner":2910,"repository":2911,"state":2936,"title":3025,"updated_at":3026,"url":3027,"score":3028},"### Environment\n\nDocs page: https://ui3.nuxt.dev/components/input\n\nSorry if this repo isn't the right place to report bugs about the docs. The \"edit this page\" link on the docs lead me to this repository. \n\nThis could be a minor thing but it's still not ideal.\n\nClicking a link on the right hand side prompts firefox if it should save the password \n\n\n\nPerhaps to mitigate this, the input field has to differ from the docs code and not use type password\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nhttps://ui3.nuxt.dev as of 28.01.2025\n\n### Reproduction\n\n1. Go to https://ui3.nuxt.dev/components/input\n2. Click a link on the right hand side\n3. Browser should ask if it should save the password\n\n### Description\n\nDocs page prompts browser to save the password due to a `\u003Cinput type=\"password\">` in an example\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3019,3020,3021],{"name":2977,"color":2978},{"name":2921,"color":2922},{"name":3022,"color":3023},"v3","49DCB8",3195,"Docs page for Input causes browser to prompt if it should save the password from a password example input","2025-01-29T10:08:23Z","https://github.com/nuxt/ui/issues/3195",0.7808481,["Reactive",3030],{},["Set"],["ShallowReactive",3033],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fs-NVTtPJEPqbeFY_QA_pMjYLXimKEJnb4HTNjt0EO6o":-1},"/nuxt/nuxt.com/1910"]