Client-only content doesn't render in component's slot
See original GitHub issueOriginal issue reported at nuxt/nuxt.js#8579.
The content inside <client-only>
tag doesn’t render when the tag is placed in a component’s slot of another component’s slot, as shown in the following reproduction:
codesandbox
@egoist any chance you could look into this issue please? I can see the repo hasn’t been updated in a while but this missing functionality is crucial for some use-cases, when client-only tag is the only way to go in the nested slots structure 😕
Issue Analytics
- State:
- Created 3 years ago
- Reactions:11
- Comments:8
Top Results From Across the Web
Client-only content doesn't render in component's slot #8579
<client-only> tag does not render its content when the tag is placed inside a component slot, as shown in the provided example.
Read more >Nuxt.js — Best practices for client-side-only contents (client ...
Nuxt.js provides a way for you to exclude those components from the server side rendering phase, which is the <client-only> or <no-ssr> ...
Read more >Vue Component do not render slots content after deployment
I do have a problem with Vue slots. If I start the local project with npm run dev the content of the slots...
Read more >No SSR - Quasar Framework
The QNoSsr component makes sense only if you are creating a SSR website/app. It avoids rendering its content on the server and leaves...
Read more >Built-in Components - Nuxt
This component is used to purposely render a component only on client-side. To import a component only on the client, register the component...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Had the same issue that I worked around by wrapping the entire component in the client only instead of the slot.
Initially, triggering the issue
The current fix, not ideal but works in our case
One tiny workaround I found for now is by removing scoping to the template and using the slot where we have to pass the component as the default slot and template. So this basically - https://codesandbox.io/s/vue-horizontal-calendar-nuxt-demo-forked-hvx9e?file=/pages/index.vue