\r\n \u003C/ClientOnly>\r\n\u003C/template>\r\n\r\n\u003Cscript setup>\r\n const childRef = ref()\r\n\r\n // ...\r\n childRef.value.childMethod()\r\n // ERROR: childRef.value.childMethod is not a function\r\n\u003C/script>\r\n```\r\n\r\n### Additional context\r\nIf you remove the `useFetch` call on `childComponent`, the exposed child method is available in the parent again \r\n\r\n### Logs\r\n\r\n_No response_",[3047,3048],{"name":3029,"color":3030},{"name":3049,"color":3050},"upstream-bug","B60205",15086,"closed","ClientOnly: using async methods breaks defineExpose","2024-09-28T02:44:01Z","https://github.com/nuxt/nuxt/issues/15086",0.65512806,{"description":3058,"labels":3059,"number":3068,"owner":3038,"repository":3038,"state":3052,"title":3069,"updated_at":3070,"url":3071,"score":3072},"### Environment\n\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v16.15.0`\r\n- Nuxt Version: `3.0.0-rc.8`\r\n- Package Manager: `yarn@3.2.3`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-ewymne?file=app.vue,components%2FHello.client.vue\n\n### Describe the bug\n\nHi 👋 I ran into this issue when trying to import a client only component with an explicit import \r\n\r\n````ts\r\nimport { Hello } from \"#components\"\r\n````\r\n\r\nHowever it seems that a .server component fallback is mandatory for Nuxt server-side, I can workaround this by adding a Hello.server.vue but i don't think that this is an expected behavior.\r\n\r\n Calling the component without specifying the import works.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3060,3063,3064,3067],{"name":3061,"color":3062},"3.x","29bc7f",{"name":3029,"color":3030},{"name":3065,"color":3066},"components","05B979",{"name":3032,"color":3033},14755,"Explicit import from #component of .client components throws an error server side","2023-01-19T17:39:45Z","https://github.com/nuxt/nuxt/issues/14755",0.66816103,{"description":3074,"labels":3075,"number":3082,"owner":3038,"repository":3038,"state":3052,"title":3083,"updated_at":3084,"url":3085,"score":3086},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v20.10.0\r\n- Nuxt Version: 3.10.3\r\n- CLI Version: 3.10.1\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: typescript, devtools, modules, css, app, imports, vite, i18n\r\n- Runtime Modules: @nuxtjs/tailwindcss@6.11.4, @nuxtjs/i18n@8.1.1, @vueuse/nuxt@10.8.0, nuxt-swiper@1.2.2, @pinia/nuxt@0.5.1\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-xnzjj4?file=app.vue\r\n\r\n### Describe the bug\r\n\r\nThe error is reproduced if you use an existing component inside \"ClientOnly\". Doesn't play when using template lang=\"html\"\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n[nitro] [unhandledRejection] ReferenceError: _component_AppIcon is not defined",[3076,3079,3080,3081],{"name":3077,"color":3078},"good first issue","fbca04",{"name":3061,"color":3062},{"name":3029,"color":3030},{"name":3032,"color":3033},26137,"Component \"ClientOnly\" does not work correctly with template lang=\"pug\"","2024-03-09T12:38:09Z","https://github.com/nuxt/nuxt/issues/26137",0.6749525,{"description":3088,"labels":3089,"number":3094,"owner":3038,"repository":3038,"state":3052,"title":3095,"updated_at":3096,"url":3097,"score":3098},"### Environment\r\n\r\n{\r\n \"name\": \"nuxt-app\",\r\n \"private\": true,\r\n \"type\": \"module\",\r\n \"scripts\": {\r\n \"build\": \"nuxt build\",\r\n \"dev\": \"nuxt dev\",\r\n \"generate\": \"nuxt generate\",\r\n \"preview\": \"nuxt preview\",\r\n \"postinstall\": \"nuxt prepare\"\r\n },\r\n \"dependencies\": {\r\n \"@ant-design-vue/nuxt\": \"^1.4.1\",\r\n \"@nuxt/ui-pro\": \"^1.2.0\",\r\n \"@pinia-plugin-persistedstate/nuxt\": \"^1.2.0\",\r\n \"@element-plus/nuxt\": \"^1.0.9\",\r\n \"element-plus\": \"^2.7.3\",\r\n \"@pinia/nuxt\": \"^0.5.1\",\r\n \"ant-design-vue\": \"^4.2.1\",\r\n \"nuxt\": \"^3.11.2\",\r\n \"vue\": \"^3.4.27\",\r\n \"vue-router\": \"^4.3.2\",\r\n \"dayjs-nuxt\": \"^2.1.9\",\r\n \"@nuxtjs/device\": \"^3.1.1\",\r\n \"@vueuse/nuxt\": \"^10.9.0\",\r\n \"jwt-decode\": \"^4.0.0\"\r\n }\r\n}\r\n\r\n\r\n### Reproduction\r\nhttps://stackblitz.com/edit/github-hn5jfw?file=components%2Ftest.vue\r\nIf defineExpose is before useFetch, there will be no error, but it cannot expose refresh?\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n### Describe the bug\r\nhttps://stackblitz.com/edit/github-hn5jfw?file=components%2Ftest.vue\r\nIf defineExpose is before useFetch, there will be no error, but it cannot expose refresh?\r\n\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3090,3091],{"name":3061,"color":3062},{"name":3092,"color":3093},"pending triage","E99695",27367,"Can't define Expose be used after the request?","2024-05-27T08:09:55Z","https://github.com/nuxt/nuxt/issues/27367",0.678995,{"description":3100,"labels":3101,"number":3104,"owner":3038,"repository":3038,"state":3052,"title":3105,"updated_at":3106,"url":3107,"score":3108},"### Environment\r\n\r\n- Operating System: `Linux`\r\n- Node Version: `v16.14.2`\r\n- Nuxt Version: `3.3.3`\r\n- Nitro Version: `2.3.2`\r\n- Package Manager: `npm@7.17.0`\r\n- Builder: `vite`\r\n- User Config: `experimental`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-a1d8zg?file=pages%2Findex.vue\r\n\r\n### Describe the bug\r\n\r\nSimilar to what https://github.com/nuxt/framework/pull/8713 resolved a while back but it seems like the issue persists for `.client.vue` files?\r\n\r\nSetting `experimental: {\r\n treeshakeClientOnly: false,\r\n },` which was the workaround for the mentioned pr does however not fix the issue\r\n\r\n### Additional context\r\n\r\n`.client` component on ssr:\r\n\r\n\r\n`.client` component on client side navigation\r\n\r\n\r\n\r\nThe `\u003Cclient-only>` wrapped component on the other hand works for both ssr and csr: \r\n\r\n\r\n\r\n\r\n### Logs\r\n\r\n_No response_",[3102,3103],{"name":3061,"color":3062},{"name":3032,"color":3033},20061,"`.client.vue` scoped styles are missing on ssr","2023-04-07T08:31:06Z","https://github.com/nuxt/nuxt/issues/20061",0.68120885,{"labels":3110,"number":3113,"owner":3038,"repository":3038,"state":3052,"title":3114,"updated_at":3115,"url":3116,"score":3117},[3111,3112],{"name":3061,"color":3062},{"name":3092,"color":3093},14410,"createClientOnly return a component that cannot transfer the ref of its child","2023-01-19T17:35:09Z","https://github.com/nuxt/nuxt/issues/14410",0.68408865,{"description":3119,"labels":3120,"number":3123,"owner":3038,"repository":3038,"state":3052,"title":3124,"updated_at":3125,"url":3126,"score":3127},"### Environment\r\n\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.8.2\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.0\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-4byrfr?file=modules%2Fcode-block.ts,app.vue\r\n\r\n### Describe the bug\r\n\r\nI have installed a vue component from NPM and created a nuxt module for it:\r\n\r\n```javascript\r\nimport { defineNuxtModule, addComponent } from '@nuxt/kit'\r\n\r\nexport default defineNuxtModule({\r\n setup() {\r\n addComponent({\r\n name: 'VCodeBlock',\r\n export: 'VCodeBlock',\r\n filePath: '@wdns/vue-code-block',\r\n mode: \"client\",\r\n })\r\n },\r\n})\r\n```\r\n\r\nHowever, despite `mode: \"client\"` whenever I put it in a nuxt page, layout or component I still get an ssr related issue\r\n\r\n```\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.\r\n[Vue warn]: Component \u003CAnonymous> is missing template or render function.\r\n```\r\nI also have the same error if I just import the component without using nuxt modules \r\nIf I completely disable SSR, it works fine. \r\n\r\nIf I remove mode client, it's worse : it says window is undefined\r\n\r\nI would assume the problem is that the module is client side... but the component use it in isn't, therefore it's rendered before it should. \r\n\r\nIt does feel like a bug however because you'd assume mode client would work. What does `mode:client` do exactly ? \r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell-script\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.\r\n[Vue warn]: Component \u003CAnonymous> is missing template or render function.\r\n```\r\n",[3121,3122],{"name":3061,"color":3062},{"name":3092,"color":3093},24478,"node_modules component in nuxt modules : I still get SSR related errors despite `mode:client`","2023-11-28T23:34:19Z","https://github.com/nuxt/nuxt/issues/24478",0.68759143,{"description":3129,"labels":3130,"number":3139,"owner":3038,"repository":3038,"state":3052,"title":3140,"updated_at":3141,"url":3142,"score":3143},"### Environment\r\n\r\n```\r\n❯ npx nuxi info\r\nNuxi 3.0.0\r\n\r\nRootDir: /home/projects/github-dpyktf-owfxvw\r\nNuxt project info: \r\n\r\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v16.14.2`\r\n- Nuxt Version: `3.0.0`\r\n- Nitro Version: `1.0.0`\r\n- Package Manager: `npm@7.17.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n```\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-dpyktf-owfxvw?file=app.vue\r\n\r\n### Describe the bug\r\n\r\n[Template refs](https://vuejs.org/guide/essentials/template-refs.html) are not available on [client-side only components](https://nuxt.com/docs/guide/directory-structure/components#client-components) defined in `.client` files.\r\n\r\nIt works as expected on components not having `.client` in their file name. It makes no difference if SSR is enabled or not. As long as a components file name ends with `.client` the ref is not set as expected on `onMounted`.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n\r\nConsole logs from the linked StackBlitz example:\r\n\r\n```\r\n{component: 'FocusInput', ref: input}\r\n{component: 'FocusInputBroken', ref: null}\r\n```\r\n",[3131,3134,3135,3136],{"name":3132,"color":3133},"documentation","5319e7",{"name":3061,"color":3062},{"name":3029,"color":3030},{"name":3137,"color":3138},"🍰 p2-nice-to-have","0E8A16",15551,"Template refs in .client components not available at `onMounted()`","2023-01-19T17:54:02Z","https://github.com/nuxt/nuxt/issues/15551",0.6876271,{"description":3145,"labels":3146,"number":3149,"owner":3038,"repository":3038,"state":3052,"title":3150,"updated_at":3151,"url":3152,"score":3153},"### Environment\n\nNuxi 3.0.0-rc.11 19:06:28\r\nRootDir: /Users/konradstraszewski/WebstormProjects/lendi-b2c 19:06:29\r\nNuxt project info: (copied to clipboard) 19:06:29\r\n\r\n------------------------------\r\n- Operating System: `Darwin`\r\n- Node Version: `v16.14.0`\r\n- Nuxt Version: `3.0.0-rc.11`\r\n- Nitro Version: `0.5.4`\r\n- Package Manager: `npm@8.19.0`\r\n- Builder: `vite`\r\n- User Config: `app`, `ssr`, `experimental`, `postcss`, `nitro`, `css`, `meta`, `modules`, `image`, `unocss`, `publicRuntimeConfig`, `vite`, `nuxtTypedRouter`, `plugins`\r\n- Runtime Modules: `nuxt-typed-router@1.2.2`, `@unocss/nuxt@0.45.22`, `@nuxt/image-edge@1.0.0-27707824.1028381`, `nuxt-jsonld@2.0.5`, `@pinia/nuxt@0.4.1`, `@vueuse/nuxt@8.9.2`, `()`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-w6cj1g-1libb7?file=nuxt.config.ts\r\n\r\n`npm run serve-demo`\r\n\n\n### Describe the bug\n\nClientSide scope doesn't set data-v-{id} properly when inlineSSRStyles is set to true.\r\n\r\nYou can see that the CSS write in pages/index.vue doesn't work properly (card should be `height: 200px`). It is because this line of code loaded from index.css refers to different data-v-{id}. When inlineSSRStyles switched to false, everything works great\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3147,3148],{"name":3061,"color":3062},{"name":3092,"color":3093},15034,"ClientSide scope doesn't set data-v-{id} properly when inlineSSRStyles is set to true.","2023-01-19T17:44:03Z","https://github.com/nuxt/nuxt/issues/15034",0.68777484,["Reactive",3155],{},["Set"],["ShallowReactive",3158],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fQdHMFMuqrIM8Ipg7ER20kywdf_kvcP-p1BNgL-GXsNg":-1},"/nuxt/nuxt/14310"]