Daniel Roe - State of Nuxt 2024 - Vuejs Amsterdam 2024

well it is such a pleasure to be here thank you so much for um the warm welcome and Alex I'll uh give you that5 pounds afterwards in just a moment um so um without further ado

uh I want to talk a little bit about the state of n but first I want to say hi um here are some of the projects I'm involved with it's not uh just next I would love you to check out for example my uh Magic rexp uh Library rex. deev um or uh find out what your first commit on GitHub is with first commit. is or some of the other things there but I will be honest n is much more exciting than any of those other things uh

this year has been a year of moves uh a year of moves for me I moved to this beautiful city in Edinburgh uh and that is not quite the view out of my uh window but that's definitely where I am based most of the time this year has also been a year of moves uh for n um the road to n 3 I think was not quite as smooth as the road in that picture I don't know who here has participated in migrating a project to KN three uh who here has perhaps

been uh waiting uh on on um eagerly or less eagerly for the release of NX 3 um but I think there are a couple of things that we learned in the process of adopting nux 3 and releasing it um one is that scope and time are not both fixed you can't both deliver a project that is as Grand as you want and do so in the time that you predict for it in advance you have to pick one of those to

be important and in releasing NX 3 we picked scope and it took a long time uh that's definitely a a learning point to put on the on the list the second was the importance of ecosystem I think if you ever want a live demonstration of the importance of waterfall you can look at the migration from view2 to view3 and then the migration from KNX 2 to KNX 3 and then the migration of any

libraries depending on N from their version two to version three modules and you really see the the power of uh of additive uh waterfalls you see the um the significance of relying on internals so uh migrating from uh n 2 modules to NX 3 modules was not straightforward because n itself changed how things were done and that was a big part of why we we've adopted a new kit model where we have an SDK for modules and so on and the whole

thing was a little bit like repairing a moving car because whilst we were building NX 3 Evan released vit thank you Evan actually I I am very grateful that Evan released meat but at the same time there were challenges it's difficult to repair a moving car and so we learned a few things migrating to n 3 um and the aim one aim of this past year has been to help people migrate to NX 3 uh for which we have NX Bridge which is a module uh

that adds a forward compatibility layer to help people move uh to KN 3 it does a lot of different things uh and it's been released stably uh and it will be around and maintained for a while particular credits to riota um who is a phenomenal member of the the KN team who is maintaining that particularly um out of curiosity um does anyone here use NX Bridge currently or do you plan on using nux Bridge do just scan the QR code uh and let me know um