-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Upgrade to vue3 would probably be recommendable #262
Comments
I would be interested in migrating, but I'd love to hear @martonlederer's thoughts on this before anyone spends a lot of time on it! |
This seems to be a crisp and pleasant summary on benefits of vue3 - esp. of the composition API: |
Thanks for sharing this! I think that Vue 3 is a great option for the site, but I think we should also consider some other options as well. The team recently reminded me that Next.js is a very valid competitor, along with React. Some more deliberation will need to occur before we can decide on anything final. |
It is most likely, that I (or we?) will recode the entire website to use the Vue 3 composition API and Typescript, but as mentioned above, we are not sure if we will use Vue or React/Next for the next major website update. A few reasons why I suggest a Vue 3 update:
|
If some of you agree, I will (try to) implement this.
https://itnext.io/how-to-migrate-from-vue-2-0-to-vue-3-0-composition-api-with-ts-part-3-create-a-global-store-aabdfa45a687
The text was updated successfully, but these errors were encountered: