Adrien Foulon

Nope not even, it was just supposed to be a clean rewrite of the project which has way too many issues but it's currently abandoned and didn't make it past...

No it's definitely not, just check [my fork](https://github.com/Tofandel/vuesax) and you'll understand just how much work was needed to make this production worthy, there is critical bugs in 70% of the...

This is not a nuxt specific issue, it is in fact a big bug of the tooltip on its own that is not being destroyed correctly, I have already fixed...

You can use the same doc as vuesax or the one in the README, there was no api change (that I recall at least) I only fixed a thousand bugs...

You need to use ifvisible.js@next, the v1 didn't have any exports in it it would just register the lib on the window

Your issue is very simple, you're not using events but props, so your methods will never be called (the casing is also wrong) Instead of ```vue :init="handleFilePondInit" :processFile="handleFilePondProcessfile" :removeFile="handleFilePondRemovefile" :addfile="handleOnaddfile"...

React contexts is basically vue's inject/provide so this should be used instead of the suggestion to add props I can have a look, it should actually be very straightforward to...

So as it seems migrating this lib to a portal would be a huge undertaking, it is possible to access the full context using a react internal in v16: `this.__reactInternalMemoizedUnmaskedChildContext`...

Please have this merged... 800Kb gzipped for this bundle this is crazy.. Vue shouldn't be bundled, and moment as well because this prevents us from removing the locales which are...

I did the same, also very happy now