\n```\n\n### Description\n\nThe issue occurs both when I run the app in development mode and when I build it for production. I tested it on Safari (Mac and iPhone) and Chrome (iPhone only). On the first page load, the animation works fine, but when I reload the page, the animation stops. However, when the component where it is used updates, the icon state changes (still without animation). \n\nHere I placed some icons randomly in the pages to show the problem and when it occurs:\n\nhttps://github.com/user-attachments/assets/ca9772d8-61bb-47da-9b9e-38cbb8d5796c\n\n).",[],361,"nuxt","icon","open","Icon is not animating correctly","2025-02-23T14:06:29Z","https://github.com/nuxt/icon/issues/361",0.67679673,{"description":1993,"labels":1994,"number":1998,"owner":1985,"repository":1999,"state":1987,"title":2000,"updated_at":2001,"url":2002,"score":2003},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v20.11.0`\r\n- Nuxt Version: `3.10.0`\r\n- CLI Version: `3.10.0`\r\n- Nitro Version: `2.8.1`\r\n- Package Manager: `pnpm@8.14.2`\r\n- Builder: `-`\r\n- User Config: `modules`, `imports`, `typescript`\r\n- Runtime Modules: `@nuxt/test-utils/module@3.11.0`\r\n- Build Modules: `-`\n\n### Reproduction\n\nhttps://github.com/lucasecdb/nuxt-context-error-repro\n\n### Describe the bug\n\nProvided value in plugin does not reach the component when using a `Symbol()` as key.\r\n\r\nYou can check the behavior by running `pnpm test` in the MRE. If you run the app using `pnpm start` and go to `http://localhost:3006` you can see the \"hello world\" string correctly.\r\n\r\n\r\n\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[1995],{"name":1996,"color":1997},"pending triage","5D08F5",750,"test-utils","Provides with Symbol not available to rendered component","2025-01-10T13:55:59Z","https://github.com/nuxt/test-utils/issues/750",0.7058502,{"description":2005,"labels":2006,"number":2007,"owner":1985,"repository":2008,"state":1987,"title":2009,"updated_at":2010,"url":2011,"score":2012},"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.70707965,{"description":2014,"labels":2015,"number":2016,"owner":1985,"repository":2008,"state":1987,"title":2017,"updated_at":2018,"url":2019,"score":2020},"i think the example code should use \r\n`// Current implementation\r\npreviousTodos.value = todos.value;\r\n\r\n// Proposed change\r\npreviousTodos.value = [...todos.value];`",[],1653,"Docs (useNuxtData => #Optimistic Updates).Incorrect Use of Reference Assignment in previousTodos.value = todos.value","2025-03-21T19:43:40Z","https://github.com/nuxt/nuxt.com/issues/1653",0.7085567,{"description":2022,"labels":2023,"number":2027,"owner":1985,"repository":1986,"state":2028,"title":2029,"updated_at":2030,"url":2031,"score":2032},"Hello,\r\n\r\nI was wondering whether there is a way to allow users to tell whether they want to allow iconify cookies or not. \r\nAfter all, for GDPR they should be able to control this behaviour!",[2024],{"name":2025,"color":2026},"question","d876e3",94,"closed","Iconify cookies","2024-12-21T12:20:21Z","https://github.com/nuxt/icon/issues/94",0.64535016,{"description":2034,"labels":2035,"number":2036,"owner":1985,"repository":1999,"state":2028,"title":2037,"updated_at":2038,"url":2039,"score":2040},"It would be really good to know why using `@nuxt/test-utils` is more beneficial than using `@vue/test-utils` in a Nuxt project. Despite the obvious point being this package is made specifically for Nuxt, `@vue/test-utils` still works perfectly well in Nuxt projects.\r\n\r\nCould we get some comparison docs (a table maybe) of what `@vue/test-utils` can't do for a Nuxt project, but `@nuxt/test-utils` can?",[],475,"@nuxt/test-utils vs @vue/test-utils?","2023-12-02T00:13:13Z","https://github.com/nuxt/test-utils/issues/475",0.6633388,{"labels":2042,"number":2052,"owner":1985,"repository":1985,"state":2028,"title":2053,"updated_at":2054,"url":2055,"score":2056},[2043,2046,2049],{"name":2044,"color":2045},"3.x","29bc7f",{"name":2047,"color":2048},"bug","d73a4a",{"name":2050,"color":2051},"vite","3574D1",11791,"Can't add Vue files as templates with Vite","2023-01-19T15:43:40Z","https://github.com/nuxt/nuxt/issues/11791",0.68234414,{"description":2058,"labels":2059,"number":2064,"owner":1985,"repository":2065,"state":2028,"title":2066,"updated_at":2067,"url":2068,"score":2069},"### For what version of Nuxt UI are you asking this question?\n\nv3.0.0-alpha.x\n\n### Description\n\nI've noticed that links (\\\u003Ca\\> tags) created with `UButton` contain a lot of unnecessary styling related to the button itself, disabled and enabled state. Given that for anchors there is no `disabled` property in the HTML specification, this means that out of the following styles:\n```\nrounded-[calc(var(--ui-radius)*1.5)] font-medium inline-flex items-center focus:outline-none transition-colors px-2.5 py-1.5 text-sm gap-1.5 ring ring-inset ring-[var(--ui-primary)]/50 text-[var(--ui-primary)] hover:bg-[var(--ui-primary)]/10 focus-visible:ring-2 focus-visible:ring-[var(--ui-primary)]\n```\n\nAt the very least, these can be removed:\n\n```\ndisabled:cursor-not-allowed aria-disabled:cursor-not-allowed disabled:opacity-75 aria-disabled:opacity-75 disabled:bg-transparent aria-disabled:bg-transparent dark:disabled:bg-transparent dark:aria-disabled:bg-transparent\n```\n\nThis is quite a reduction in classes and can make a moderate difference in total page size and even web vitals scores, especially if there are a lot of links on the page created with `UButton` (which is very likely given the customization UButton provides with icons, variants, colors, and more)\n\nIn order to make this work, the classes that rely on disabled state would likely need to be extracted into a separate place in the theme, which tailwind-variants will then need to merge if there is no `to` property present.\n\nYou might be asking why, given that technically people can rely on it to prevent navigation until a certain condition. But the answer to that is that restricting links like that is generally bad practice and can be circumvented pretty easily. It's not meant to be a security feature and it also lacks in terms of functional purpose.\n\nI'll check to see what I can do about it, but I thought sharing it here would be more beneficial in case someone will be faster than me in preparing a PR for this =)",[2060,2061],{"name":2025,"color":2026},{"name":2062,"color":2063},"v3","49DCB8",2907,"ui","[Performance improvement opportunity]: remove disabled-dependent classes on links created with `UButton`","2025-01-13T22:45:37Z","https://github.com/nuxt/ui/issues/2907",0.6936552,{"description":2071,"labels":2072,"number":2076,"owner":1985,"repository":1985,"state":2028,"title":2077,"updated_at":2078,"url":2079,"score":2080},"\r\nFirst up: I don't know if this is the right project to post it, but it might be in the intrest of the Less.js project to work with vite, I hope.\r\n\r\n\r\n### Environment\r\n\r\n- `less` version: 4.2.0\r\n- `nodejs` version: 20.9.0\r\n- vite@5.0.10\r\n- nuxt@3.9.0\r\n- `operating system`: debian\r\n\r\n\r\n### Error\r\n\r\n```\r\n[vite-node] [plugin:vite:vue] [SyntaxError] ./node_modules/.pnpm/nuxt@3.9.0_less@4.2.0_vite@5.0.10/node_modules/nuxt/dist/app/components/nuxt-root.vue:3:5\r\n```\r\n\r\n```\r\n ERROR Pre-transform error: @vnode-* hooks in templates are no longer supported. Use the vue: prefix instead. For example, @vnode-mounted should be changed to @vue:mounted. @vnode-* hooks support has been removed in 3.4.\r\n```\r\n\r\n\r\n### Reproduction\r\n\r\ncodesandbox.io\r\n1. nuxt3 framework\r\n2. template with lang=\"less\" (aktually not needed, having installed by `pnpm` and runnung `npm run dev` through nuxi->vite is enough to error out)\r\n\r\nand it brakes.\r\n\r\n### Describe the bug\r\n\r\n\u003C!-- A clear and concise description of what the bug is -->\r\n\r\n**Expected behavior:**\r\n\r\nto work with vite\r\n",[2073,2074],{"name":2044,"color":2045},{"name":1996,"color":2075},"E99695",25142,"error on compiling using less","2024-01-10T17:43:59Z","https://github.com/nuxt/nuxt/issues/25142",0.6941065,{"description":2082,"labels":2083,"number":2086,"owner":1985,"repository":1985,"state":2028,"title":2087,"updated_at":2088,"url":2089,"score":2090},"### Describe the feature\n\nWhen you have `extend`, `include` or `mixin` in a vue pug template, the following error happens. \r\n\r\n`[vite] Internal server error: the \"basedir\" option is required to use includes and extends with \"absolute\" paths`\r\n\r\nIn Vue3, you can avoid this error by giving `basedir ` value to `vitejs/plugin-vue` as below.\r\n\r\n```\r\nimport {defineConfig} from 'vite'\r\nimport vue from '@vitejs/plugin-vue'\r\n\r\n\r\nexport default defineConfig({\r\n plugins: [\r\n vue({\r\n template: {\r\n preprocessOptions: {\r\n basedir: __dirname\r\n }\r\n }\r\n }),\r\n ],\r\n})\r\n```\r\n\r\nBut in nuxt project, there seems no way.\r\n\r\nI tried to configure the same way. \r\n```\r\nexport default defineNuxtConfig({\r\n vite: {\r\n plugins: [\r\n vue({\r\n template: {\r\n preprocessOptions: {\r\n basedir: __dirname,\r\n },\r\n },\r\n }),\r\n ],\r\n },\r\n});\r\n```\r\n\r\nBut it ended up with this error.\r\n\r\n```ERROR At least one \u003Ctemplate> or \u003Cscript> is required in a single file component. #2```\r\n\r\nIt happens because of the same vue plugin being injected twice. \r\n\r\nMy suggestion is that we add the addressed option to the vite setting\r\nhttps://github.com/nuxt/framework/blob/837c93849941e49a90da627f6d31f3d4bd0d4d4d/packages/vite/src/vite.ts#L81\r\n\r\nAlthough my example sets the root dir to `basedir`, it could be __dirname +`/assets` instead for example.\r\n\r\n\r\nA use case in which `extend`, `include` or `mixin` is needed is migration projects from traditional web sites which utilize those techniques. \r\n\r\n\r\n\n\n### Additional information\n\n- [X] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://v3.nuxtjs.org/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/framework/discussions) and [issues](https://github.com/nuxt/framework/issues).",[2084,2085],{"name":2044,"color":2045},{"name":1996,"color":2075},15746,"Enable `extend`, `include` or `mixin` in a pug vue template","2023-01-22T19:26:11Z","https://github.com/nuxt/nuxt/issues/15746",0.6977356,["Reactive",2092],{},["Set"],["ShallowReactive",2095],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"DB6YrqAfA-G_waKexp874wNxv9jnAkRCrBr19AJNb7Y":-1},"/nuxt/test-utils/485"]