Open jshimkoski opened 3 years ago
You can wrap v-calendar
in a <client-only>
tag
You can wrap
v-calendar
in a<client-only>
tag
That is more of a workaround than a clean solution.
<client-only>
is not guaranteed to exist, which in turn prompts them to have to include an additional dependency.<client-only>
tag, the user will see pop-in on page load.Yes, we all typically develop within guard rails, and that includes adhering to what is required by a third party component. However, when the solution to this issue is pretty straightforward, it eliminates all of the workarounds, and it makes v-calendar more robust at the same time, doesn't that make it worth it?
And what about this?
And what about this?
I tested it and it seems working for me. I'll use it for my project. If there are issues, I'll comment here
Here is an example. https://stackblitz.com/edit/nuxt-starter-rf7flv?file=app.vue
And what about this?
I tested it and it seems working for me. I'll use it for my project. If there are issues, I'll comment here
Here is an example. https://stackblitz.com/edit/nuxt-starter-rf7flv?file=app.vue
Is v-date-picker available in this way? Data binding via attributes works exactly. However, the selected date cannot be imported.
is there any progress on supporting SSR natively through the package?
I have a custom SSR scenario (so no client-only) and am wondering if the library now supports ssr?
@runxc1 You can install the client-only component
I ended up having to go with another library as the client-only library isn't an option, I've ran into some issues with it.
V-calendar should support SSR.
I see in your vue.config.js file you have extractCSS set to false. This is the primary reason SSR support is broken (if you extract the CSS, the document not found error will likely go away, this is a shortcoming of Vue-cli).
Would it be possible to have two different builds? One with extractCSS set to false, and another with extractCSS set to true?
That way, you could have the current version and an SSR compatible build as well.