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

Upgrade to vue3 would probably be recommendable #262

Open
michael-spengler opened this issue Sep 11, 2020 · 4 comments
Open

Upgrade to vue3 would probably be recommendable #262

michael-spengler opened this issue Sep 11, 2020 · 4 comments

Comments

@michael-spengler
Copy link
Contributor

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

@t8
Copy link
Member

t8 commented Sep 11, 2020

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!

@michael-spengler
Copy link
Contributor Author

This seems to be a crisp and pleasant summary on benefits of vue3 - esp. of the composition API:
https://www.youtube.com/watch?v=6HUjDKVn0e0

@t8
Copy link
Member

t8 commented Sep 13, 2020

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.

@martonlederer
Copy link
Member

martonlederer commented Sep 27, 2020

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:

  • Composition API makes everything more readable
  • Typescript is already the main language of nest.land, it makes sense to use it in our site
  • The whole repo needs some cleanup and simplification

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

3 participants