Nuxt Nation 2023: Anthony Fu - Now, and the Future of Nuxt DevTools

[Music] hello everyone so yeah I'm so glad to be here at n Nation so today let's talk about uh now and the future of nextstep tool so so a bit about myself my name is anony Fu and aing member of n be and view and I'm a creator of VI use vest slide window CSS and L and currently

working at next Lab on the framework team so uh first let's uh discuss a bit about the reason why we Built noxd tool so as you might know that's n focusing a lot on the developer experience so uh we have uh build we have provide file based routing to save you uh from manually writing your routing file and we have

the very powerful module ecosystem um that allow you to in integrating with third party service with one click and while the modules handling are the best practice for you and we also have the the very first H module replacement inherent from V and we have also service ey rendering that's each components in your next app can be working isomorphically either by server rendered or client rendered based on needed and with a lot more like nitro with zero

config with age rendering with middleware with components Auto Import composable Auto Import and a lot more so um we're trying to provide all those things that we think that can be beneficials to provide better developer experience but have you ever like wondered like what's the what's the cost of having them so in overview that we can see that uh we have introduced many conventions to reduce the need of having body plate or code duplications help helping us to

uh organize our code uh or projects uh better and we also uh introduce quite uh quite some obstructions in order to shift uh the comp complexity from user app to our framework so that when you are building an app using Nu you can focusing more on your own logic instead of woring about the technical details of how BND how BND Works Etc and we Al trying to provide the the best sensible

defaults that makes the KN work out of book uh without with zero configuration while making the best practice for you to delivery uh your app with the best performance and user experience we also put quite some efforts in terms of normalizations of uh the under the underlying tools uh with unplugging we smooth out the difference between weback and beat um that this make next Works uh supporting both uh interchangeably based on your needs and

with nitron we make deployments easier than ever that's with with your exactly same code base you can deploy your app to any hosting service like verell nety or even hosting your own node or D no servers like without changing any opal code so those features are super awesome but we have to admit that uh the a big sacrifice we have to have to do is to

sacrifice a little bit of the transparency as the tradeoff of having those features by transparency I mean the ability to see uh what is going on under the hood uh for example like the cost of learning and understanding each features that KN provide this tradeoff is invadable and as for any tools that you have to learn it before you can use it right so but uh that's let see that what we could make it better here so