\n\u003C/UDropdownMenu>\n```\n\n### Logs\n\n```shell-script\n\n```",[2956,2958,2961],{"name":2927,"color":2957},"d73a4a",{"name":2959,"color":2960},"needs reproduction","CB47CF",{"name":2962,"color":2963},"v3","49DCB8",3546,"`UAvatar` doesn't trigger `UDropdownMenu`","2025-03-28T17:43:01Z","https://github.com/nuxt/ui/issues/3546",0.6932544,{"description":2970,"labels":2971,"number":2974,"owner":2871,"repository":2938,"state":2930,"title":2975,"updated_at":2976,"url":2977,"score":2978},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v18.18.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: npm@10.2.3\r\n- Builder: -\r\n- User Config: modules, devtools\r\n- Runtime Modules: @pinia/nuxt@0.5.1, @nuxt/test-utils/module@3.10.0\r\n- Build Modules: -\n\n### Reproduction\n\n[Minimal reproduction](https://stackblitz.com/edit/github-ftohct?file=app.nuxt.test.ts)\n\n### Describe the bug\n\nHi all! Do I understand correctly that on the current version of `@nuxt/test-utils` there is no way to pre-fill a store using this instruction from the [Pinia](https://pinia.vuejs.org/cookbook/testing.html#Initial-State) documentation.\r\n\r\n```\r\nimport { describe, test, expect, vi } from 'vitest';\r\nimport { createTestingPinia } from '@pinia/testing';\r\nimport { mountSuspended } from '@nuxt/test-utils/runtime';\r\nimport App from './app.vue';\r\n\r\nconst siteInfoMock = {\r\n title: 'Nuxt 3',\r\n url: 'https://nuxt.com',\r\n};\r\n\r\ndescribe('App link', async () => {\r\n const wrapper = await mountSuspended(App, {\r\n global: {\r\n plugins: [\r\n createTestingPinia({\r\n initialState: {\r\n Site: {\r\n siteInfo: siteInfoMock,\r\n },\r\n },\r\n createSpy: vi.fn,\r\n }),\r\n ],\r\n },\r\n });\r\n\r\n test('Should render the link with a substitute title', () => {\r\n expect(wrapper.get('[data-test-id=\"link\"]').text()).toBe(\r\n siteInfoMock.title\r\n );\r\n\r\n // The test passes because the data in the \"Site\" store has not been changed.\r\n // expect(wrapper.get('[data-test-id=\"link\"]').text()).toBe('Example.com');\r\n });\r\n\r\n test('Should render the link with the spoofed link', () => {\r\n expect(wrapper.get('[data-test-id=\"link\"]').attributes().href).toBe(\r\n siteInfoMock.url\r\n );\r\n\r\n // The test passes because the data in the \"Site\" store has not been changed.\r\n // expect(wrapper.get('[data-test-id=\"link\"]').attributes().href).toBe('https://example.com');\r\n });\r\n});\r\n```\r\nThe component is also rendered, receiving default data from the store. In turn, I expect replacement data in the store.\r\n\r\nI tried to look for information about a similar case in local chats and here in different threads, but I just didn’t receive any information. Several users have raised a similar issue.\r\n\r\n* https://discordapp.com/channels/473401852243869706/1199858451833168004/1199858605831241820\r\n* https://discordapp.com/channels/473401852243869706/496371343542059011/1195669478403489862\r\n* https://discordapp.com/channels/473401852243869706/496371343542059011/1153407426087886942\r\n\r\nIt seems like `@pinia/nuxt` & `@nuxt/test-utils` are not fully compatible, namely the `createTestingPinia` & `mountSuspended` methods.\r\n\r\nPlease tell me, someone was able to solve the problem of how to create a test instance of Pinia.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nstdout | createSuspenseBoundary (/home/projects/rlmilwjxk.github/node_modules/.pnpm/@vue+runtime-core@3.4.15/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:1439:43)\r\n\u003CSuspense> is an experimental feature and its API will likely change.\r\n\r\nstderr | warn$1 (/home/projects/rlmilwjxk.github/node_modules/.pnpm/@vue+runtime-core@3.4.15/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:46:13)\r\n[Vue warn]: App already provides property with key \"Symbol(pinia)\". It will be overwritten with the new value.\n```\n",[2972],{"name":2868,"color":2973},"5D08F5",737,"mountSuspended & createTestingPinia","2024-11-28T08:58:33Z","https://github.com/nuxt/test-utils/issues/737",0.69712037,{"description":2980,"labels":2981,"number":2989,"owner":2871,"repository":2871,"state":2930,"title":2990,"updated_at":2991,"url":2992,"score":2993},"### Environment\n\n------------------------------\r\n- Operating System: `Darwin`\r\n- Node Version: `v16.16.0`\r\n- Nuxt Version: `3.0.0-rc.9`\r\n- Nitro Version: `0.5.0`\r\n- Package Manager: `pnpm@7.11.0`\r\n- Builder: `vite`\r\n- User Config: `typescript`, `css`, `components`, `modules`, `runtimeConfig`, `vglStore`\r\n- Runtime Modules: `~/nuxt-modules/routes-module.ts`, `@pinia/nuxt`, `@vueuse/nuxt@9.2.0`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-cyy9sn?file=app.vue\n\n### Describe the bug\n\nI'm constantly forgetting to add `.value` when working with refs and wondered why eslint is not helping me – no visual hints in VS Code and no error when running eslint in terminal.\r\nThere is a rule from `eslint-plugin-vue` to catch this: [vue/no-ref-as-operand](https://eslint.vuejs.org/rules/no-ref-as-operand.html)\r\nTurns out, the auto imported `ref` from `#imports` is somehow \"different\" than directly importing from `vue`.\r\nIf I do `import { ref } from 'vue'`, I get squiggly lines in VS Code and `.value` is automatically added when I save the file.\r\nSee also simple reproduction above.\r\n\r\n```vue\r\n\u003Cscript setup lang=\"ts\">\r\n// uncomment this will throw vue/no-ref-as-operand\r\n// import { ref } from 'vue';\r\n\r\n// uncomment this will not help\r\n// import { ref } from '#imports';\r\n\r\nconst count = ref(1);\r\n\r\n// NOTE: should be count.value\r\nconst foo = count + 1;\r\n\r\nconsole.log(foo);\r\n\u003C/script>\r\n```\r\n\r\nNot sure if this should be fixed in `eslint-plugin-vue` or here.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2982,2983,2986],{"name":2898,"color":2899},{"name":2984,"color":2985},"3.x","29bc7f",{"name":2987,"color":2988},"upstream","E8A36D",14882,"auto imported `ref` will not trigger `vue/no-ref-as-operand` warning from eslint-plugin-vue","2024-04-09T08:17:09Z","https://github.com/nuxt/nuxt/issues/14882",0.69972914,["Reactive",2995],{},["Set"],["ShallowReactive",2998],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fepDzuK5ePaBX1ScC1vumc4SCoN_n8_BNGnzuz06y0zs":-1},"/nuxt/scripts/432"]