Migrating from 2 to 3 was a little rough??!?! A little?!!? A LITTLE?!?!?
breezycodes
Great video! That transition between Nuxt 2 > and Nuxt 3 was pretty painful. For me, the most frustrating part, as you mentioned, was how long it took for modules/packages to get caught up
JohnKomarnicki
I'm sooo not hyped for this major release too. And I'm sooo happy too.
ZyncInteractive
Once I've heard a very nice description of what perfect development cycle and process should look like - it should be boring. That's the whole point. You make an estimation, you deliver an estimation without unexpected roadblocks. You deliver it on time without sudden scope creep. It works out of the box without urgent patches required. A major version update that doesn't put any stress on you when you think about migration is the show case of Nuxt dev team craftsmanship.
ivanbragin
Looks like Vue 4 will take a similar approach which I'm relieved about. The migration was very painful, though has made our development processes far smoother and it would be a difficult sell to do it again to the powers that be. I love Vue the way it is atm tbh, only thing I could ask for is more optimisations, performance improvements, that kind of thing atm.
Wozza
I just started a new work project in Nux t 3 😩
nyagah
A series covering the unjs ecosystem would be so great. Thanks for your amazing content
matanon
Do you think the new Nuxt certificate worth it
Like the senior one
Would i learn more advanced stuff or it's just best practice stuff and stuff like that that you can find on YouTube And udemy
mr__mh
I am so so glad that when I decided to learn Vue/Nuxt I started with Vue3/Nuxt3. I don't know what Vue2/Nuxt2 was like but I LOVE script setup and Vue3/Nuxt3!
toddhammer
I hope Nuxt continues to improve in the coming years. I don't want to learn another framework, but currently, I can't find many Vue/Nuxt job opportunities.
pepinogdev
I had to migrate an entire production ready environment from nuxt 2 to nuxt 3. All the while trying to keep the functionality and the code readable. And oh boy was it fun. Documentation was lacking. I had to browse a lot of source code and do a bunch of testing to see what works and what doesn't. Implement rudimentary versions of modules that did not exist. Migrate dependencies from Vue 2 to 3. Not to mention Nuxt changed the way it did data fetching at least twice between minor versions. So, every latest version meant making sure I'm getting the right data at the right moment.
Needless to say, I'm glad Nuxt is not breaking itself anymore. Please let this be the norm going forwards. :fingers-crossed:
dorogans
So, it's no longer Nuxt 3, it's just Nuxt
wvovaw
Already? Please fix the problems first
namaefumei
I'm happy for that, start using Nuxt 3 right now for serious... hope that 4 has a simple migration flow xD
caiovinicius
Not hyped but very happy. Hope this helps me convince more react 16 users to jump ship.
Gaijin
We almost finished migration from Nuxt 2 to Nuxt 3.
Again 😢
TarasShabatin
Let's just trust Daniel, no explanation needed1
scottyzen
I just use vanilla vuejs 😂. I’ll wait until the creator of vue gives me a better solution.
jaymartinez
we wanted to write an app in nuxt 3 back then, but it was so unstable and finally we ended up with nextjs and react
