\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\nand the test file looks like this:\r\n\r\n\r\n```\r\n// TestA.spec.ts\r\nimport { describe, it, expect } from 'vitest';\r\nimport { mount } from '@vue/test-utils';\r\nimport TestA from './TestA.vue';\r\n\r\ndescribe('Competition TestA', () => {\r\n it('renders component', async () => {\r\n const wrapper = mount(TestA);\r\n expect(wrapper.text()).toContain('Client component here...');\r\n });\r\n});\r\n\r\n```\r\n\r\nFinally, the client component:\r\n\r\n```\r\n// ClientComponent.client.vue\r\n\u003Ctemplate>\r\n \u003Cdiv>Client component here...\u003C/div>\r\n\u003C/template>\r\n```\r\n\r\nIf I remove the \".client\" from the component file name (to make it just ClientComponent.vue), then the tests will run and pass normally. However, there are some cases where I want to use \".client\" to make sure it's only rendered client-side.\r\n\r\n### Reproduction \r\nhttps://stackblitz.com/edit/github-ndby6m?file=components/TestA.spec.ts\r\n\r\nFailures can be seen there by running `pnpm run test`",[2062],{"name":2063,"color":2064},"vitest-environment","b60205","test-utils","Tests fail when using .client components","2023-12-02T00:27:10Z","https://github.com/nuxt/test-utils/issues/555",{"labels":2070,"number":2078,"owner":1991,"repository":1991,"state":2009,"title":2079,"updated_at":2080,"url":2081,"score":2082},[2071,2072,2075],{"name":2028,"color":2029},{"name":2073,"color":2074},"3.x","29bc7f",{"name":2076,"color":2077},"nitro","bfd4f2",12158,"update azure swa workflow documentation","2023-01-19T15:59:16Z","https://github.com/nuxt/nuxt/issues/12158",0.7392616,{"description":2084,"labels":2085,"number":2089,"owner":1991,"repository":1992,"state":2009,"title":2090,"updated_at":2091,"url":2092,"score":2093},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.10.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.15.0\n- Builder: -\n- User Config: compatibilityDate, future, devtools, modules, css\n- Runtime Modules: @nuxt/ui-pro@3.0.0-alpha.12, @nuxt/content@3.1.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.12\n\n### Reproduction\n\n```vue\n\u003Cscript setup>\nconst route = useRoute();\n\nconst navigation = ref([\n {\n title: 'Announcement bar',\n to: {\n path: route.path,\n query: {\n ...route.query,\n collection: 'Announcement bar'\n }\n },\n active: true\n },\n {\n title: 'Hero',\n to: {\n path: route.path,\n query: {\n ...route.query,\n collection: 'Hero'\n }\n },\n active: false\n }\n])\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUContentNavigation :navigation=\"navigation\" variant=\"link\" />\n\n \u003Cpre>\n {{ navigation }}\n \u003C/pre>\n\u003C/template>\n```\n\n### Description\n\nIn V2 I could make links active by query values. Somehow in V3 it looks like it fully ignores my current `active` state. Even tho the values are hardcoded now.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2086,2087,2088],{"name":2002,"color":2003},{"name":1988,"color":1989},{"name":2006,"color":2007},3266,"`UContentNavigation` can't handle custom `active` states","2025-02-27T21:22:55Z","https://github.com/nuxt/ui/issues/3266",0.74293196,{"labels":2095,"number":2103,"owner":1991,"repository":1991,"state":2009,"title":2104,"updated_at":2105,"url":2106,"score":2107},[2096,2099,2102],{"name":2097,"color":2098},"good first issue","fbca04",{"name":2100,"color":2101},"pending triage","E99695",{"name":2031,"color":2032},5212,"example(pug): not working in Nuxt 2.4.5","2023-01-22T15:33:01Z","https://github.com/nuxt/nuxt/issues/5212",0.743517,["Reactive",2109],{},["Set"],["ShallowReactive",2112],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"Nb6KRYqtYYOHoFb7S222EFBKt_SgmT5IA3VWfnqsny4":-1},"/nuxt/ui/2115"]