mst101/vue-datepicker

A datepicker Vue component. Compatible with Vue 3.x.

Datepicker

A datepicker Vue component compatible with Vue 3.x.

N.B. For Vue 2.x, please use version 4.x.

• Features
• Documentation
• Contribution
• License

N.B. This is a fork from @sum.cumo/vue-datepicker to which I have previously contributed but which is no longer maintained. That project was originally forked from vuejs-datepicker which is licensed under the MIT license. Thanks to the original creators for the great work.

Features

• accepts keyboard input
• keyboard navigable
• internationalized
• disable dates
• highlight dates
• inline calendar
• auto-alignment
• compatible with Bootstrap
• custom slots
• append to body

Documentation

Checkout the vuepress Documentation. There you will also find the Demo pages and the Migration guide.

Contribution

Please feel free to open up an issue or provide a pull request.

License

Copyright 2023 Mark Thompson

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

vue-datepicker's Issues

Popup.vue render error

In a project that's transitioning from Vue 2 to Vue 3 we decided to swap from @sum.cumo/vue-datepicker 5.0.0 to version 6.0.0 of this fork. When launching the page we had an issue with this line:

vue-datepicker/src/components/Popup.vue

Line 98 in ca0bb3e

return h('div', this.$slots.default()[0].children.default())

.
We got an error that default in this.$slots.default() was not a function. We were able to fix this issue locally by changing the line to return h('div', this.$slots.default[0].children.default());
Is this because of our Vue 3 transition, or is this an issue with the Popover component? We were confused because we'd expect the repository's demo page to not work correctly if this was an issue with the component itself, but that page works.
If it's an issue with the Popover component, we're happy to submit a PR with our change!