Damon Muma

Totally came to vueuse thinking this might be a thing they'd have as a beautiful complement to useDraggable. Looking at the code it is less straightforward than i might have...

Whether or not they function completely, I think a simple way to globally mock supported browser APIs makes everyone's legitimate web targeted code less likely to throw exceptions once it...

I've created a localValue mixin for issues like this: ``` export default { props: ['value'], computed: { localValue: { get() { return this.value; }, set(value) { this.$emit('input', value); } }...

This is intended behaviour. I agree that it shouldn't be like this, but [this commit](https://github.com/vuejs-tips/v-money/pull/2) explicitly sets this as the normal behaviour (despite contradicting how inputs normally work).

Really important for any library like this. I imagine implementing accessibility with something based on canvas would be a huge ordeal, but maybe as a less crazy alternative it could...

I see from testing, that this isn't fixed in Storybook 8 with or without vue-component-menat. This is really, really needed. Script setup is the standard way of writing Vue components...

@JorgeMorata I don't think an example repo is necessary to demonstrate this. It would just be nice for the build to continue in spite of missing assets.. sort of like...

Say you have an error that makes one link on one page out of 100000 not work. It’s nice if that doesn’t stop the whole site from working. Sure it’s...

I'm having a similar issue. I'm looking at the line ``` var warn = Vue.util.warn ``` and a bit confused how this would ever work in Vue 3, though! In...

After some digging my own issue is related to the postinstall hook on vue-demi having run at some point and decided that the project was a Vue 2 project. Similarly...