\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`",[2919],{"name":2920,"color":2921},"vitest-environment","b60205","test-utils","Tests fail when using .client components","2023-12-02T00:27:10Z","https://github.com/nuxt/test-utils/issues/555",{"description":2927,"labels":2928,"number":2932,"owner":2872,"repository":2873,"state":2887,"title":2933,"updated_at":2934,"url":2935,"score":2936},"### 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```",[2929,2930,2931],{"name":2883,"color":2884},{"name":2869,"color":2870},{"name":2898,"color":2899},3266,"`UContentNavigation` can't handle custom `active` states","2025-02-27T21:22:55Z","https://github.com/nuxt/ui/issues/3266",0.7248255,{"description":2938,"labels":2939,"number":2942,"owner":2872,"repository":2873,"state":2887,"title":2943,"updated_at":2944,"url":2945,"score":2946},"### Description\n\nThe Landing Card hover effect is very nice and could be used in other components like buttons, intput fields, toolbars or modals.\r\nIt would be great to have it available as a directive or a composable or whatever suits best these use cases.\n\n### Additional context\n\n\r\n",[2940,2941],{"name":2866,"color":2867},{"name":2898,"color":2899},2112,"[Nuxt UI Pro] - Provide the \u003CULandingCard> hover effect with a directive so we can use it in buttons or other components.","2024-09-10T16:29:24Z","https://github.com/nuxt/ui/issues/2112",0.73009455,{"description":2948,"labels":2949,"number":2956,"owner":2872,"repository":2872,"state":2887,"title":2957,"updated_at":2958,"url":2959,"score":2960},"### Describe the feature\n\n### Describe the feature\r\n\r\nPlease add \r\nhttps://github.com/nuxt/framework/commit/ede534847831f46c45089a122d19b083d2ae26c7\r\n\r\nto your documentation. We had our app running with IIS10 + nuxt2 and had no problem at all. With Nuxt3 we struggled, but that documentation of the archived repo helped us alot!\r\n\r\nCould you please add this to the Nuxt Docs in the deployment section?\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://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2950,2953],{"name":2951,"color":2952},"documentation","5319e7",{"name":2954,"color":2955},"3.x","29bc7f",20499,"[DOC] IIS Support","2023-07-27T12:26:24Z","https://github.com/nuxt/nuxt/issues/20499",0.731269,{"description":2962,"labels":2963,"number":2971,"owner":2872,"repository":2872,"state":2887,"title":2972,"updated_at":2973,"url":2974,"score":2975},"### Environment\n\nhttps://codesandbox.io/s/github/nuxt/starter/tree/v3-codesandbox/?file=/nuxt.config.ts\r\n\n\n### Reproduction\n\nOpen code sandbox from documentation listed as example of https://nuxt.com/docs/guide/concepts/vuejs-development\r\n\r\ngo to nuxt.config comment link and see broken link\n\n### Describe the bug\n\nThe link provided in the comments of nuxt.congif is wrong and should be updated to `https://nuxt.com/docs/guide/directory-structure/nuxt.config`\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2964,2967,2968],{"name":2965,"color":2966},"good first issue","fbca04",{"name":2954,"color":2955},{"name":2969,"color":2970},"🧹 p1-chore","FEF2C0",12477,"Update Nuxt documentation link in code sandbox","2023-01-19T16:06:26Z","https://github.com/nuxt/nuxt/issues/12477",0.7337963,{"description":2977,"labels":2978,"number":2982,"owner":2872,"repository":2872,"state":2887,"title":2983,"updated_at":2984,"url":2985,"score":2986},"### Describe the feature\n\nIn https://nuxt.com/docs/api/composables/use-fetch#usefetch, there are some types statically written in markdown, which are outdated (if you compare them to the types in nuxt 3.3.1). e.g. the `header` property accepts different values now.\r\n\r\nI could add a PR to fix these static types, or maybe it would be better to not include them into the docs hand-written, and refer to the file in the git? Or maybe it's possible to include the file dynamically from git?\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://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2979,2981],{"name":2866,"color":2980},"8DEF37",{"name":2951,"color":2952},18637,"sync types from code base into docs","2024-08-01T07:15:47Z","https://github.com/nuxt/nuxt/issues/18637",0.7345523,["Reactive",2988],{},["Set"],["ShallowReactive",2991],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fNb6KRYqtYYOHoFb7S222EFBKt_SgmT5IA3VWfnqsny4":-1},"/nuxt/ui/2115"]