Not sure if this is due to my recent PR, or if its because I accidentally bumped flatpickr to 2.4.3 when pulling in the new vue-bulma-datepicker.
However, I encountered an issue along the lines of node[i] is not a function in flatpickr's triggerEvent function.
Whilst getting to the bottom of it, I removed the datepicker.set('onChange', ...) hook from the components mounted() function.
This resolved the issue whilst maintaining proper reactivity
Not sure if this is due to my recent PR, or if its because I accidentally bumped flatpickr to 2.4.3 when pulling in the new vue-bulma-datepicker. However, I encountered an issue along the lines of
node[i] is not a function
in flatpickr'striggerEvent
function.Whilst getting to the bottom of it, I removed the
datepicker.set('onChange', ...)
hook from the componentsmounted()
function. This resolved the issue whilst maintaining proper reactivity