\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,"Icon is not animating correctly","2025-02-23T14:06:29Z","https://github.com/nuxt/icon/issues/361",0.71945137,{"description":2042,"labels":2043,"number":2046,"owner":1991,"repository":2047,"state":1993,"title":2048,"updated_at":2049,"url":2050,"score":2051},"### Environment\n\nThis is one of the environments i came across the problem:\r\n[11:15:23 AM] Working directory: /Users/lorenzorottigni/Documents/gitlab_private/portfolio.rottigni.tech\r\n[11:15:23 AM] Nuxt project info: (copied to clipboard)\r\n\r\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v18.13.0\r\n- Nuxt Version: 3.9.3\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: yarn@1.22.21\r\n- Builder: vite\r\n- User Config: ssr, debug, srcDir, serverDir, test, app, modules, css, postcss, unocss, tailwindcss, googleFonts, i18n, nitro, pwa, image, delayHydration, extensions, typescript, builder, vite, vue, runtimeConfig, devServer, sourcemap, experimental\r\n- Runtime Modules: @vueuse/nuxt@10.7.2, @nuxtjs/tailwindcss@6.10.4, @pinia/nuxt@0.5.1, @unocss/nuxt@0.58.3, @nuxtjs/i18n@8.0.0, @nuxt/image@1.3.0, nuxt-jsonld@2.0.8, @kevinmarrec/nuxt-pwa@0.17.0, @nuxtjs/google-fonts@3.1.3, nuxt-calendly@0.1.18, nuxt-delay-hydration@1.3.3, @nuxt/test-utils/module@3.10.0\r\n- Build Modules: -\r\n------------------------------\r\n\r\n[11:15:23 AM] 👉 Report an issue: https://github.com/nuxt/nuxt/issues/new\r\n\r\n👉 Suggest an improvement: https://github.com/nuxt/nuxt/discussions/new\r\n\r\n👉 Read documentation: https://nuxt.com\n\n### Reproduction\n\nThe crucial file is MyComponent.spec.ts:\r\nhttps://stackblitz.com/~/github.com/LorenzoRottigni/nuxt-test-utils-vitest-spy\n\n### Describe the bug\n\nI'm currently facing challenges in testing a component method within a Nuxt environment. Specifically, I'm attempting to spy on a component method to test its interactions within template events. Despite researching similar cases online, I've yet to find a clear solution to this issue.\r\n\r\nOne suggestion I encountered was to define the spy before the component mounts. However, I'm unable to access `wrapper.vm` before mount time, complicating this approach. Additionally, I experimented with spying on the global injected `$fetch` method from the 'ofetch' library. Unfortunately, this led to another error regarding the inability to redefine the variable `$fetch` when attempting variations like:\r\n\r\n```javascript\r\nimport OFetch from 'ofetch'\r\nconst spy = vi.spyOn(OFetch, '$fetch')\r\n// or\r\nconst spy = vi.spyOn(global, '$fetch')\r\n// or\r\nconst spy = vi.spyOn({ $fetch }, '$fetch')\r\n```\r\n\r\nIt appears that this issue may not be directly tied to the nuxt-test-utils package. Nevertheless, I wanted to bring it to your attention in the hopes that someone might offer guidance or assistance. I'm eager to find a resolution and would appreciate any insights or suggestions you might have.\r\n\r\nI'm also considering reporting a similar issue to the vue-test-utils package, as I suspect that this problem might be reproducible outside of the Nuxt environment.\r\n\r\nThank you for your time and assistance.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2044],{"name":2026,"color":2045},"5D08F5",763,"test-utils","Unable to use vitest spy within nuxt 3 component methods.","2024-05-28T15:28:23Z","https://github.com/nuxt/test-utils/issues/763",0.7228493,{"description":2053,"labels":2054,"number":2056,"owner":1991,"repository":1992,"state":2057,"title":2058,"updated_at":2059,"url":2060,"score":2061},"We can create a component for this that will allow us to use it on modules and agencies",[2055],{"name":1985,"color":1986},1195,"closed","[Agencies]: add not found layout if no result","2023-02-15T12:31:15Z","https://github.com/nuxt/nuxt.com/issues/1195",0.65610725,{"description":2063,"labels":2064,"number":2068,"owner":1991,"repository":2047,"state":2057,"title":2069,"updated_at":2070,"url":2071,"score":2072},"Any usage of NuxtLink lead to an error \r\n\r\n```\r\n[Vue warn]: Failed to resolve component: RouterLink\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement. \r\n at \u003CNuxtLink to= { name: 'index', params: { userId: '123' } } class=\"text-neutral-501\" onClick=fn\u003ConLinkClick> > \r\n at \u003CUserLink userId=\"123\" ref=\"VTU_COMPONENT\" > \r\n at \u003CVTUROOT>\r\n```\r\n\r\n[Reproduction](https://stackblitz.com/edit/nuxt-vitest-rgzrs9?file=components%2FUserLink.vue)\r\n\r\n",[2065],{"name":2066,"color":2067},"vitest-environment","b60205",590,"Failed to resolve component: RouterLink","2023-12-02T00:37:12Z","https://github.com/nuxt/test-utils/issues/590",0.68823534,{"description":2074,"labels":2075,"number":2076,"owner":1991,"repository":1992,"state":2057,"title":2077,"updated_at":2078,"url":2079,"score":2080},"https://www.figma.com/file/OLlmzoVQ7FSBh4FJJORNpl/%F0%9F%96%A5---nuxt.com?node-id=5246%3A48502",[],543,"[Community] Nuxters page integration `/community/nuxters`","2023-02-15T12:32:30Z","https://github.com/nuxt/nuxt.com/issues/543",0.69221425,{"description":2082,"labels":2083,"number":2076,"owner":1991,"repository":2047,"state":2057,"title":2085,"updated_at":2086,"url":2087,"score":2080},"```\r\nnpm WARN ERESOLVE overriding peer dependency\r\nnpm WARN While resolving: vitest-environment-nuxt@0.10.0\r\nnpm WARN Found: vitest@0.33.0\r\nnpm WARN node_modules/vitest\r\nnpm WARN peer vitest@\">=0.30.1 \u003C1\" from @vitest/ui@0.33.0\r\nnpm WARN node_modules/@vitest/ui\r\nnpm WARN @vitest/ui@\"^0.33.0\" from nuxt-vitest@0.10.0\r\nnpm WARN node_modules/nuxt-vitest\r\nnpm WARN 1 more (vitest)\r\nnpm WARN 2 more (nuxt-vitest, the root project)\r\nnpm WARN\r\nnpm WARN Could not resolve dependency:\r\nnpm WARN peer vitest@\"^0.24.5 || ^0.26.0 || ^0.27.0 || ^0.28.0 || ^0.29.0 || ^0.30.0\" from vitest-environment-nuxt@0.10.0\r\nnpm WARN node_modules/vitest-environment-nuxt\r\nnpm WARN vitest-environment-nuxt@\"0.10.0\" from nuxt-vitest@0.10.0\r\nnpm WARN node_modules/nuxt-vitest\r\nnpm WARN\r\nnpm WARN Conflicting peer dependency: vitest@0.30.1\r\nnpm WARN node_modules/vitest\r\nnpm WARN peer vitest@\"^0.24.5 || ^0.26.0 || ^0.27.0 || ^0.28.0 || ^0.29.0 || ^0.30.0\" from vitest-environment-nuxt@0.10.0\r\nnpm WARN node_modules/vitest-environment-nuxt\r\nnpm WARN vitest-environment-nuxt@\"0.10.0\" from nuxt-vitest@0.10.0\r\nnpm WARN node_modules/nuxt-vitest\r\n```\r\n\r\n```\r\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v18.16.1\r\n- Nuxt Version: ^3.6.3\r\n- Nitro Version: -\r\n- Package Manager: unknown\r\n- Builder: webpack\r\n- User Config: extends, devtools, appConfig, vite, nitro, routeRules, site, webVitals, typescript, colorMode, app, modules, googleFonts, runtimeConfig\r\n- Runtime Modules: @nuxt/devtools@^0.6.7, @nuxtjs/supabase@^0.3.8, @nuxtjs/google-fonts@^3.0.1, @nuxthq/ui@^2.5.0, @pinia/nuxt@^0.4.11, @pinia-plugin-persistedstate/nuxt@^1.1.1, @nuxtjs/web-vitals@^0.2.6, nuxt-capo@^0.1.0, @nuxtjs/fontaine@^0.4.0, @nuxt/content@^2.7.0, nuxt-simple-sitemap@^3.0.11, nuxt-seo-experiments@^3.0.5, nuxt-vitest@^0.10.0 \r\n- Build Modules: -\r\n------------------------------\r\n```",[2084],{"name":2066,"color":2067},"upgrading to latest giving error","2023-12-02T00:32:09Z","https://github.com/nuxt/test-utils/issues/543",["Reactive",2089],{},["Set"],["ShallowReactive",2092],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"QuW28bIO7KK1Hlz-K3VaSsRvESSbnOJw_78s3jjKKjQ":-1},"/nuxt/test-utils/524"]