\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```",[1984,1987],{"name":1985,"color":1986},"bug","d73a4a",{"name":1988,"color":1989},"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.61008686,{"description":1999,"labels":2000,"number":2007,"owner":1991,"repository":2008,"state":1993,"title":2009,"updated_at":2010,"url":2011,"score":2012},"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.",[2001,2004],{"name":2002,"color":2003},"enhancement","a2eeef",{"name":2005,"color":2006},"vitest-environment","b60205",531,"test-utils","nuxt server environment support","2025-03-06T16:28:47Z","https://github.com/nuxt/test-utils/issues/531",0.68146104,{"description":2014,"labels":2015,"number":2016,"owner":1991,"repository":2017,"state":1993,"title":2018,"updated_at":2019,"url":2020,"score":2021},"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.68469834,{"description":2023,"labels":2024,"number":2028,"owner":1991,"repository":1992,"state":1993,"title":2029,"updated_at":2030,"url":2031,"score":2032},"### Description\n\nHow to configure Nuxt Color Mode in Nuxt UI so that it does not inject color styles for all Nuxt UI components using inline styles",[2025],{"name":2026,"color":2027},"question","d876e3",3394,"implement csp, sty-src with nonce","2025-02-25T10:13:42Z","https://github.com/nuxt/ui/issues/3394",0.69070905,{"description":2034,"labels":2035,"number":2040,"owner":1991,"repository":1992,"state":1993,"title":2041,"updated_at":2042,"url":2043,"score":2044},"### Description\n\nHello. How can i use provide in programmatically modal usage?",[2036,2037],{"name":2026,"color":2027},{"name":2038,"color":2039},"v3","49DCB8",2987,"Provide in modal programmatically usage","2024-12-31T05:16:08Z","https://github.com/nuxt/ui/issues/2987",0.6910803,{"description":2046,"labels":2047,"number":2048,"owner":1991,"repository":2049,"state":1993,"title":2050,"updated_at":2051,"url":2052,"score":2053},"The latest version v1.11.0 does not properly resolve the auto imported type of `Icon`\n\nWith the previous v1.10.3 - the auto imported `Icon` component shows a type error if missing props and also shows available props in the VS Code context window:\n\n\n\nWith v1.11.0 - the `Icon` component does not show any type errors if missing props and the available props are not displayed by VS Code:\n\n\n\nUsing dependencies:\n\n```json\n{\n \"@nuxt/icon\": \"1.11.0\",\n \"nuxt\": \"^3.16.0\",\n \"vue\": \"^3.5.13\",\n \"vue-router\": \"^4.5.0\"\n}\n```\n\nWith latest nuxt config:\n\n```ts\nexport default defineNuxtConfig({\n compatibilityDate: '2024-11-01',\n devtools: { enabled: true },\n modules: ['@nuxt/icon']\n})\n```",[],373,"icon","Auto Import Types Not Resolving in latest v1.11.0","2025-03-19T00:11:46Z","https://github.com/nuxt/icon/issues/373",0.7008195,{"description":2055,"labels":2056,"number":2060,"owner":1991,"repository":2049,"state":2061,"title":2062,"updated_at":2063,"url":2064,"score":2065},"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?",[2057],{"name":2058,"color":2059},"upstream","B4199A",257,"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.6488022,{"description":2067,"labels":2068,"number":2070,"owner":1991,"repository":1992,"state":2061,"title":2067,"updated_at":2071,"url":2072,"score":2073},"Issue closed",[2069],{"name":2002,"color":2003},2095,"2025-01-29T14:49:08Z","https://github.com/nuxt/ui/issues/2095",0.66789544,{"description":2075,"labels":2076,"number":2082,"owner":1991,"repository":1992,"state":2061,"title":2083,"updated_at":2084,"url":2085,"score":2086},"### 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?",[2077,2078,2079],{"name":2026,"color":2027},{"name":2038,"color":2039},{"name":2080,"color":2081},"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.67144275,{"description":2088,"labels":2089,"number":2095,"owner":1991,"repository":1992,"state":2061,"title":2096,"updated_at":2097,"url":2098,"score":2099},"### 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_",[2090,2093,2094],{"name":2091,"color":2092},"duplicate","cfd3d7",{"name":2002,"color":2003},{"name":2038,"color":2039},2531,"Allow custom colors in app.config.ts","2024-11-13T12:09:04Z","https://github.com/nuxt/ui/issues/2531",0.6789761,["Reactive",2101],{},["Set"],["ShallowReactive",2104],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"4EuQnlTpNv74xB5JyfWg0AE9Nkq_0OKc82N5t8-yCz0":-1},"/nuxt/test-utils/1120"]