\n\nBrowser: `Google Chrome Version 134.0.6998.89 (Official Build) (arm64)`\n\nAlso reproduced on `Safari Version 18.3.1 (20620.2.4.11.6)`\n\n### Description\n\nUser may want to copy the text in the query input of a `select-menu` component by moving cursor around text, now it's unable to do it without a keyboard (`Shift + left/right arrow` or `Cmd/Ctrl + A` to select all).\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2856,2859],{"name":2857,"color":2858},"bug","d73a4a",{"name":2860,"color":2861},"triage","ffffff",3583,"nuxt","ui","open","Accessibility: unable to select text in the query input of a select-menu","2025-03-17T00:34:07Z","https://github.com/nuxt/ui/issues/3583",0.610966,{"description":2871,"labels":2872,"number":2879,"owner":2863,"repository":2880,"state":2865,"title":2881,"updated_at":2882,"url":2883,"score":2884},"We currently support running composables/components in a browser-type environment (with happy-dom, and soon jsdom). But there are use cases where it might be useful to support running tests in a hybrid server environment where things like h3 utilities and nuxt ssr utilities work.\r\n\r\nThis could definitely be classed as non-essential and experimental, but we can track it here.",[2873,2876],{"name":2874,"color":2875},"enhancement","a2eeef",{"name":2877,"color":2878},"vitest-environment","b60205",531,"test-utils","nuxt server environment support","2025-03-06T16:28:47Z","https://github.com/nuxt/test-utils/issues/531",0.67421967,{"description":2886,"labels":2887,"number":2888,"owner":2863,"repository":2889,"state":2865,"title":2890,"updated_at":2891,"url":2892,"score":2893},"The current example [deployment](https://nuxt.com/deploy/github-pages) script generates warnings due to the actions using deprecated versions.\r\n\r\nI also use `pnpm` locally, so an example of how to get started with `pnpm` as well as `npm` would be nice.\r\n\r\nI'm not sure what the preset does in `npx nuxt build --preset github_pages` and if that's the same as the [Nitro preset](https://nitro.unjs.io/deploy/providers/github-pages)?\r\n\r\nMy own static page could be deployed using `pnpm generate` with this `deploy.yaml` script:\r\n\r\n```yaml\r\n# https://github.com/actions/deploy-pages#usage\r\nname: Deploy to GitHub Pages\r\n\r\non:\r\n push:\r\n branches: [main]\r\n\r\n workflow_dispatch:\r\n\r\n# Grant GITHUB_TOKEN the permissions required to make a Pages deployment\r\npermissions:\r\n contents: read\r\n pages: write # to deploy to Pages\r\n id-token: write # to verify the deployment originates from an appropriate source\r\n\r\njobs:\r\n build:\r\n runs-on: ubuntu-latest\r\n steps:\r\n - name: Checkout\r\n uses: actions/checkout@v4\r\n - name: Setup PNPM\r\n uses: pnpm/action-setup@v3\r\n with:\r\n version: 9.0.x\r\n - name: Setup Node\r\n uses: actions/setup-node@v4\r\n with:\r\n node-version: \"20\"\r\n # Pick your own package manager and build script\r\n - name: Install dependencies\r\n run: pnpm install\r\n - name: Build nuxt\r\n run: pnpm generate\r\n - name: Upload artifact\r\n uses: actions/upload-pages-artifact@v3\r\n with:\r\n path: ./.output/public\r\n\r\n # Deployment job\r\n deploy:\r\n environment:\r\n name: github_pages\r\n url: ${{ steps.deployment.outputs.page_url }}\r\n needs: build\r\n runs-on: ubuntu-latest\r\n steps:\r\n - name: Deploy to GitHub Pages\r\n id: deployment\r\n uses: actions/deploy-pages@v4\r\n```\r\n\r\nI'm hesitant to update the docs with this example myself when I don't fully understand it all yet, but maybe this could be useful as a starter to someone with more knowledge then me (or future me).\r\n\r\nI took some inspiration from the [Vitepress](https://vitepress.dev/guide/deploy#github-pages) example, which is why a couple of things have been moved or reformatted slightly.\r\n\r\n---\r\n\r\nEdit: remove `- run: corepack enable` as I don't think its necessary.",[],1578,"nuxt.com","PNPM Deployment to GitHub Pages","2024-09-26T14:12:35Z","https://github.com/nuxt/nuxt.com/issues/1578",0.7013936,{"description":2895,"labels":2896,"number":2903,"owner":2863,"repository":2864,"state":2865,"title":2904,"updated_at":2905,"url":2906,"score":2907},"### Description\n\nHello. How can i use provide in programmatically modal usage?",[2897,2900],{"name":2898,"color":2899},"question","d876e3",{"name":2901,"color":2902},"v3","49DCB8",2987,"Provide in modal programmatically usage","2024-12-31T05:16:08Z","https://github.com/nuxt/ui/issues/2987",0.7018439,{"description":2909,"labels":2910,"number":2914,"owner":2863,"repository":2915,"state":2916,"title":2917,"updated_at":2918,"url":2919,"score":2920},"While working on a new project with new developers we stumbled upon this silent failure.\r\nWe had Icons exported from Figma in the format:\r\n\r\n- iconCalendar.svg\r\n- iconPerson.svg\r\n- ...\r\n\r\nWhich were then loaded as customCollection via NuxtConfig\r\n\r\n```\r\nicon: {\r\n customCollections: [\r\n {\r\n prefix: 'theme-icon',\r\n dir: './assets/icons'\r\n },\r\n ],\r\n },\r\n```\r\n\r\nThe message upon restart was reassuring that all icons were loaded and should be accessible.\r\n\r\n```\r\nNuxt Icon loaded local collection theme-icon with 43 icons.\r\n```\r\n\r\n\r\nBut we could not access them, or better said, we could only access the ones which only were lowercase. So I digged down the whole integration with the following waypoints:\r\n\r\n- https://github.com/nuxt/icon/blob/main/src/collections.ts\r\n- https://github.com/nuxt/icon/blob/main/src/runtime/components/svg.ts#L41\r\n- https://github.com/iconify/iconify/blob/main/components/vue/src/iconify.ts#L18\r\n- https://github.com/iconify/iconify/blob/main/packages/core/src/storage/functions.ts#L86\r\n- https://github.com/iconify/iconify/blob/main/packages/utils/src/icon/name.ts#L23\r\n- https://github.com/iconify/iconify/blob/main/packages/utils/src/icon/name.ts#L90\r\n\r\nIn words:\r\n\r\n- The collection gets loaded and auto-detects all svg files within the collection folder. It also validates if the content is valid and loads them into the internal collection of nuxt-icon. \r\n- Then when called by the Component integration it gets converted/added to the Iconify component which then goes down its library path to add it to the/a custom collection for display.\r\n- This in fact validates the name given and will NOT add it if its invalid thus not displaying any icon with invalid names.\r\n- No error handling is done for this in the Component (addIcon in fact returns success which could be handled)\r\n- No validation is done when creating/loading the nuxt-icon collection.\r\n\r\n---\r\n\r\n**Suggested resolution:** For better DX there should also be a name validation when loading the collection and it should warn about all icons not following the convention. I can craft the corresponding PR.\r\n\r\n---\r\n\r\nDid I miss something elsewhere or is my deduction of the error correct?",[2911],{"name":2912,"color":2913},"upstream","B4199A",257,"icon","closed","Invalid Icon filenames, as defined/validated by Iconify, are silently failing","2024-11-21T18:24:05Z","https://github.com/nuxt/icon/issues/257",0.6567464,{"description":2922,"labels":2923,"number":2925,"owner":2863,"repository":2864,"state":2916,"title":2922,"updated_at":2926,"url":2927,"score":2928},"Issue closed",[2924],{"name":2874,"color":2875},2095,"2025-01-29T14:49:08Z","https://github.com/nuxt/ui/issues/2095",0.6615731,{"description":2930,"labels":2931,"number":2937,"owner":2863,"repository":2864,"state":2916,"title":2938,"updated_at":2939,"url":2940,"score":2941},"### For what version of Nuxt UI are you suggesting this?\n\nv3-alpha\n\n### Description\n\nI've defined my custom color in `app.vue`:\n```\n\u003Cstyle>\n@theme {\n --color-foobar-50: #f3f1ff;\n --color-foobar-100: #ebe5ff;\n...\n```\nand defined this as primary color in `app.config.ts`:\n```\nexport default defineAppConfig({\n ui: {\n colors: {\n primary: 'foobar',\n...\n```\n\nThis causes a type error:\n> Type '\"foobar\"' is not assignable to type 'Color | undefined'.\n\nThe only workaround seems to be `'foobar' as any`. However, I'd like to avoid both `as` and `any` in my code base.\n\n### Additional context\n\n_No response_",[2932,2935,2936],{"name":2933,"color":2934},"duplicate","cfd3d7",{"name":2874,"color":2875},{"name":2901,"color":2902},2531,"Allow custom colors in app.config.ts","2024-11-13T12:09:04Z","https://github.com/nuxt/ui/issues/2531",0.6782244,{"description":2943,"labels":2944,"number":2950,"owner":2863,"repository":2864,"state":2916,"title":2951,"updated_at":2952,"url":2953,"score":2954},"### 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?",[2945,2946,2947],{"name":2898,"color":2899},{"name":2901,"color":2902},{"name":2948,"color":2949},"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.6786288,{"description":2956,"labels":2957,"number":2959,"owner":2863,"repository":2864,"state":2916,"title":2960,"updated_at":2961,"url":2962,"score":2963},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v20.15.1\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: -\n- Package Manager: pnpm@9.12.3\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@2.19.2, @nuxt/image@1.8.1, @formkit/auto-animate@0.8.2\n- Build Modules: -\n\n### Version\n\nv2.19\n\n### Reproduction\n\nAlready added in description\n\n### Description\n\nI have 2 inputs\n\nI want when I press enter on input2 the focus changes to input1.\n\nThis behaviour working fine with normal **input** but not with **UInput** \n\n**Working example input**\n\n```\n\u003Ctemplate>\n \u003Cdiv>\n \u003Cinput\n ref=\"firstInput\"\n v-model=\"firstValue\"\n @keyup.enter=\"handleFirstInputEnter\"\n placeholder=\"First Input\"\n />\n \u003Cinput\n ref=\"secondInput\"\n v-model=\"secondValue\"\n @keyup.enter=\"handleSecondInputEnter\"\n placeholder=\"Second Input\"\n />\n \u003C/div>\n\u003C/template>\n\n\u003Cscript setup>\nimport { ref } from \"vue\";\n\nconst firstInput = ref(null);\nconst secondInput = ref(null);\n\nconst firstValue = ref(\"\");\nconst secondValue = ref(\"\");\n\nconst handleFirstInputEnter = () => {\n // Any specific logic for first input enter\n};\n\nconst handleSecondInputEnter = () => {\n // Switch focus back to first input when enter is pressed in second input\n firstInput.value.focus();\n};\n\u003C/script>\n```\n\n**Not working example UInput**\n\n```\n\u003Ctemplate>\n \u003Cdiv>\n \u003CUInput\n ref=\"firstInput\"\n v-model=\"firstValue\"\n @keyup.enter=\"handleFirstInputEnter\"\n placeholder=\"First Input\"\n />\n \u003CUInput\n ref=\"secondInput\"\n v-model=\"secondValue\"\n @keyup.enter=\"handleSecondInputEnter\"\n placeholder=\"Second Input\"\n />\n \u003C/div>\n\u003C/template>\n\n\u003Cscript setup>\nimport { ref } from \"vue\";\n\nconst firstInput = ref(null);\nconst secondInput = ref(null);\n\nconst firstValue = ref(\"\");\nconst secondValue = ref(\"\");\n\nconst handleFirstInputEnter = () => {\n // Any specific logic for first input enter\n};\n\nconst handleSecondInputEnter = () => {\n // Switch focus back to first input when enter is pressed in second input\n firstInput.value.focus();\n};\n\u003C/script>\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2958],{"name":2857,"color":2858},2841,"ref is not working probably for \u003CUInput>","2024-12-06T14:44:22Z","https://github.com/nuxt/ui/issues/2841",0.68412066,{"description":2965,"labels":2966,"number":2970,"owner":2863,"repository":2863,"state":2916,"title":2971,"updated_at":2972,"url":2973,"score":2974},"Despite SSR as false on the configuration, i have a \r\n\"document is not defined\" or \"window is not defined\"\r\n\r\nnuxt Config file\r\n```\r\nplugins: [{ src: '~/plugins/vuehoteldatepicker', ssr: false }],\r\n build: {\r\n vendor: ['axios','vue-hotel-datepicker'],\r\n```\r\nPlugin file\r\n```\r\nimport Vue from 'vue'\r\nimport VueHotelDatepicker from 'vue-hotel-datepicker'\r\n\r\nVue.use(VueHotelDatepicker)\r\n\r\nexport default VueHotelDatepicker\r\n```\r\n\r\nPage\r\n```\r\n\u003Ctemplate>\r\n \u003Csection class=\"container\">\r\n \u003CVueHotelDatepicker format=\"DD/MM/YYYY\">\r\n \u003C/VueHotelDatepicker>\r\n \u003C/section>\r\n\u003C/template>\r\n\r\n\u003Cscript>\r\nimport VueHotelDatepicker from '~/plugins/vuehoteldatepicker'\r\nexport default {\r\n head () {\r\n return {\r\n title: 'Test'\r\n }\r\n },\r\n components: {\r\n VueHotelDatepicker: VueHotelDatepicker\r\n }\r\n}\r\n\u003C/script>\r\n\r\n```\r\n\r\nI need some help :) Did i something wrong ?\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/c1784\">#c1784\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2967],{"name":2968,"color":2969},"2.x","d4c5f9",2009,"Despite SSR = false, ... Error \"ReferenceError: document is not defined\"","2023-01-18T15:42:55Z","https://github.com/nuxt/nuxt/issues/2009",0.6888961,["Reactive",2976],{},["Set"],["ShallowReactive",2979],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f4EuQnlTpNv74xB5JyfWg0AE9Nkq_0OKc82N5t8-yCz0":-1},"/nuxt/test-utils/1120"]