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
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.
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.
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 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 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 UA-cam And udemy
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.
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
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.
Super hyped that everyone is not hyped ✨
vid partly inspired by your comment on that one github issue 🙏
Migrating from 2 to 3 was a little rough??!?! A little?!!? A LITTLE?!?!?
Straight up gaslighting lol
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
I'm sooo not hyped for this major release too. And I'm sooo happy too.
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.
facts. definitely helps that it’s not coinciding with new vue versions or major vite changes
@@LearnVue so how will they account for major changes in Vue and Vite?
@@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.
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.
I just started a new work project in Nux t 3 😩
A series covering the unjs ecosystem would be so great. Thanks for your amazing content
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 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!
We almost finished migration from Nuxt 2 to Nuxt 3.
Again 😢
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:
So, it's no longer Nuxt 3, it's just Nuxt
hopefully. that’ll mean that each Nuxt version isn’t completely different
Only if VueJs agree 😂
@@squidproxy136 I think Vue and Nuxt sort of need to mimic the relationship between ReactJS and NextJS. It will help with the major releases.
@@LearnVue laughs in Angular
I'm happy for that, start using Nuxt 3 right now for serious... hope that 4 has a simple migration flow xD
Any updates on vapormode?
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
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 UA-cam And udemy
Not hyped but very happy. Hope this helps me convince more react 16 users to jump ship.
I just use vanilla vuejs 😂. I’ll wait until the creator of vue gives me a better solution.
unless you need SSR support, stick to pure Vue
Already? Please fix the problems first
which problems are you having?
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.
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
I hope this means getting rid of vue2/nuxt2 and bridge fully
Let's just trust Daniel, no explanation needed1
👍
I’m hyped nonetheless
i waited for about serverless things
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.
try it again, trust me
try again and again mf, til u get it.
I don't see what the benefit is of not using it anymore if you really like it and won't have this issue with it again.
now nuxt gonna be like next. gazilion versions
tbh would rather more versions with easier upgrades
Hey old friend! And no, just once a year ;)
why will nuxt4 release? nuxt 3 enough for everything
2:36 😅
Any updates on vapormode?