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
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.
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.
@@neneodonkor Depends on the breaking changes of these packages. Vite 5 was already bumped without a new Nuxt major as most changes there could be incorporated under the hood.
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!
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.
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:
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 RU-vid And udemy
How can you be hyped? Why is Nuxt 4 coming too soon ??? What the actual hell???? How many times do I need to re-write every single project that I have !!!! Guys WTF.... Nuxt 3 isn't even stable yet
Nuxt is wonderful on so many levels. The way I see it, the problem in adoption and migration has less to do with Nuxt 2 -> 3, but more precisely with Vue 2 -> 3. Seems to me that Vue lost its initial charm - simplicity and approach-ability to many devs. I too went through the unpleasant migration between Nuxt 2 -> 3, as well as Vue's options -> composition API, and yeah, the composition API is worth the hassle especially for medium+ projects. But I totally get why the Vue community & buzz in general seemed to diminish over the past 2 years. The benefit is not immediately evident.
The damage has been done. I was enjoying nuxt 2. when nuxt 3 came out i tried and overwhelmed, ultimately made me quite / find alternatives. Though pure svelte and astro is my choice now for any project i can think off but i really miss the developer experience of nuxt. which was a pure joy and heaven for any developer. It is sad that a shining open source project like nuxt which had a great future lost so many users and attraction of it due to its one single decision regardless of having the best debugging feature of any framework. So now nuxt 4 5 6 whatever... meh. damage is deep nuxt. sorry.
