-
Notifications
You must be signed in to change notification settings - Fork 180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
List of central vue libraries with their Vue3 compatibility status #30
Comments
https://awesomejs.dev/for/vue/ also has a |
Thank you @Akryum, That really is helpful. What does the
I am hoping to start answering this kind of question here for starters. @BlackSonic what do you think? |
Hi @elevatebart |
thank you @ktquez, Adding now |
There you go, added now. I hope it's good enough. |
tsParticles Vue component has a 3.x version: You can see them here The packages are: |
Thank you @matteobruni I will add it too. Would you mind adding a link to:
|
Thats an awesome idea! Can you make a PR out of it? |
Thanks @elevatebart |
@BlackSonic I thought about it last night and there are advantages to issues:
There are downsides as well:
|
Progress of?
The packages are both on
They are both available on
Vue 2.x docs Vue 3.x docs |
Thank you @matteobruni I added tsParticle to the list. But I don't feel good about it. What would you imagine be the story of a user of Do you still think tsParticle should be in such a list? |
This is a good point, I'll create a doc that explains how to migrate to the Vue 3.x version. Since Vue 2.x is more popular for now I'd like to support the 2.x version for some time. |
Thank you @matteobruni Agreed, keep me posted. When the migration docs are ready I can add them to this list. |
@elevatebart the migration instructions are here: https://github.com/matteobruni/tsparticles/blob/master/components/vue3/README.md#migrating-from-vue-2x-to-vue-3x |
Newcomers don't go straight to the issues section I think, it remains hidden to many people |
@BlackSonic you are absolutely right, discoverability is the key. I don't like the idea of such a small independent piece of data being dissolved in the bigger Readme. I will ask around to people that are trying the migration what they would rather have. The place I would like to find it when migrating would probably be in the vue v3 docs. What do you think? |
I will stop updating this issue, |
will nativescript be integrated ? So quasar 2 will have native build ? |
Hello @eeerrrttty You might wan to go ask those questions to the maintainers of those 2 libraries. |
Objective:
Guide developers in their migration from vue 2 to vue 3, specifically in their dependencies
Contents
The text was updated successfully, but these errors were encountered: