-
Notifications
You must be signed in to change notification settings - Fork 6
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
Use Vue V3 #3
Comments
This project is built using nuxt framework and vue 2. But many existing components from online resources are built with the latest version of vue, vue 3. There are some compatibility issues between these two versions. To avoid them and make the development easier, it is worthwhile to explore the possibility to move the entire project from vue 2 to vue 3. We also need to consider the compatibility between nuxt framework and vue. |
Nuxt 2.x uses Vue 2.x by default. It provides an option to use Vue 3 with Nuxt, by adding the composition-api (see the post). Now we are using "eslint-module" in our project. Since so far everything works fine, I suggest we continue with Vue 2.x as switch to a new buildModule might cause some compatibility issue (given that we just got some external modules tuned). Only if we plan to make use of some new features from Vue 3.x (e.g. teleport, fragments), we can think about it. |
Note that the incoming Nuxt 3 structure will use Vue 3 as the default framework language, for more information see their roadmap slideshow. |
Great summary! I agree that it's probably best to hold off for now.
If I understood it correctly, the composition API can already be used with nuxt 2 (point something), so that might be interesting to explore seperately. See https://composition-api.nuxtjs.org/getting-started/introduction |
@geek-yang can you edit this post to explain what and why this would be useful?
The text was updated successfully, but these errors were encountered: