Skip to content
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

Closed
elevatebart opened this issue Oct 16, 2020 · 20 comments
Closed

Comments

@elevatebart
Copy link

elevatebart commented Oct 16, 2020

Objective:

Guide developers in their migration from vue 2 to vue 3, specifically in their dependencies

Contents

  • name of library
  • name of the branch where the vue 3 work has started
  • how to install the vue 3 compatible version
  • The GH issue where the progress is tracked
  • if the author(s) has started documenting how to migrate from vue 2 to vue 3, add a link to the docs.
Framework Branch name npm install GH Issue # Docs
NuxtJS - - 5708
Gridsome vue-next - 1289
Quasar vue3-work - 7836
vuepress vuepress-next (other repo) - 2550
NativeScript-Vue rigor789/nativescript-vue-next (fork) nativescript-vue@next 583
Library Branch name npm install GH Issue # Docs
vuetify next - - Notion board
bootstrap-vue lamebear/vue3 (fork) - 5196
buefy - - 2505
chakra-ui - - 116
element-ui element-plus (other repo) element-plus 20061
inkline - - 207
oruga oruga-next (monorepo) oruga-next
Tool Branch name npm install GH Issue # Docs
Vue Formulate axwalker/support-vue-3 (fork) - 198
@testing-library/vue vue3 - -
vue-apollo v4 - 1011 V4 docs (Vue 3)
vue-meta next - 558
vue-axe vue-axe-next (other repo) vue-axe@beta 1 demo site
vee-validate next vee-validate@next 2670
vuelidate next vuelidate@next 2.0 V2 docs
Workbench Branch name npm install GH Issue # Docs
Storybook - - 10654
Vue Styleguidist next - 997
Component Branch name npm install GH Issue # Docs
vue-multiselect - - 1291
vue2-leaflet vue-leaflet (other repo) - 455
tiptap - - 735
tsParticles vue3 particle.vue3 -
vue-live next vue-live@next 54
vue-prism-editor feature/next vue-prism-editor@alpha 90
@Akryum
Copy link

Akryum commented Oct 17, 2020

https://awesomejs.dev/for/vue/ also has a vue version 3 tag in blue

@elevatebart
Copy link
Author

Thank you @Akryum,

That really is helpful.

What does the vue version 3 tag mean on awesome vue?
In other words, is there a way to see the definition of such a tag?

  • Is the library is compatible with vue 3 in its latest instance?
  • Does it have a version compatible with vue 3? on what channel? how to install it?
  • Is this is the distribution of the library that you should take that contain the vue 3 version?

I am hoping to start answering this kind of question here for starters.
Though, I am not sure this table should live here for too long.

@BlackSonic what do you think?

@ktquez
Copy link

ktquez commented Oct 17, 2020

Hi @elevatebart
vue-axe has a version for Vue 3 in this vue-axe-next repository.

@elevatebart
Copy link
Author

thank you @ktquez,

Adding now

@elevatebart
Copy link
Author

elevatebart commented Oct 17, 2020

There you go, added now. I hope it's good enough.
@ktquez tell me if I missed any info and thanks again.

@matteobruni
Copy link
Contributor

tsParticles Vue component has a 3.x version: You can see them here

The packages are: particles.vue and particles.vue3

@elevatebart
Copy link
Author

elevatebart commented Oct 17, 2020

Thank you @matteobruni

I will add it too.

Would you mind adding a link to:

  • How you track progress (GH issue, docs)?
  • The npmjs channel where people can install the vue 3 version
  • The branch where it is developed
  • If applicable the documentation on how to upgrade from vue 2 to vue 3?

@sonicoder86
Copy link
Owner

Thats an awesome idea! Can you make a PR out of it?

@ktquez
Copy link

ktquez commented Oct 17, 2020

Thanks @elevatebart

@elevatebart
Copy link
Author

@BlackSonic I thought about it last night and there are advantages to issues:

  • Comments are easy
  • Github creates deep links between repositories when one puts a link to an issue
    • The issue linked gets a reference to this issue
  • Anybody (me in this case) can create it without the author's permission (Mouhahahaha !!! 😈😈 )

There are downsides as well:

  • No pull request possible
  • No suggestion template

@matteobruni
Copy link
Contributor

Thank you @matteobruni

I will add it too.

Would you mind adding a link to:

  • How you track progress (GH issue, docs)?

Progress of?

  • The npmjs channel where people can install the Vue 3 version

The packages are both on npmjs: particles.vue for 2.x and particles.vue3 for 3.x

  • The branch where it is developed

They are both available on master but the new features branch is dev

  • If applicable the documentation on how to upgrade from Vue 2 to Vue 3?

Vue 2.x docs
https://github.com/matteobruni/tsparticles/blob/master/components/vue/README.md

Vue 3.x docs
https://github.com/matteobruni/tsparticles/blob/master/components/vue3/README.md

@elevatebart
Copy link
Author

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 particle.vue for vue 2 would want to migrate his work to vue 3?
I think I was not clear. I do not want to create a list of packages that have a vue 3 version.
I am trying to help devs migrate their codebase to vue 3 by checking their dependencies and providing useful links.

Do you still think tsParticle should be in such a list?

@matteobruni
Copy link
Contributor

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.

@elevatebart
Copy link
Author

Thank you @matteobruni

Agreed, keep me posted. When the migration docs are ready I can add them to this list.

@matteobruni
Copy link
Contributor

@sonicoder86
Copy link
Owner

Newcomers don't go straight to the issues section I think, it remains hidden to many people

@elevatebart
Copy link
Author

@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 would not even know where to put it.

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.
@NataliaTepluhina, @phanan, @bencodezen

What do you think?

@elevatebart elevatebart changed the title Add a List of central vue libraries with the record of their compatibility status List of central vue libraries with their Vue3 compatibility status Oct 19, 2020
@elevatebart
Copy link
Author

I will stop updating this issue,
All future updates will be done here

vuejs/awesome-vue#3544

@eeerrrttty
Copy link

will nativescript be integrated ? So quasar 2 will have native build ?

@elevatebart
Copy link
Author

Hello @eeerrrttty You might wan to go ask those questions to the maintainers of those 2 libraries.
The column issue will point you to the right place to start the conversation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants