How Vite Makes Nuxt Possible, Daniel Roe, ViteConf 2022

foreign [Music] my name is Daniel Rowe I'm one of the team working on building next and I'm here today to talk about how Veet makes nuts possible it is a real pleasure to be looking around and seeing so many interesting speakers representing many different Frameworks and to be here as part of a growing body of people using Veet to

build amazing things so it feels like our family in lots of ways and I love learning from from everyone else and thought it would be helpful to share maybe a little bit about how we are using Veet in next first just a quick word about my myself my my background is that immediately before I was uh part of the team uh working on myself I was uh heading up a small software as a service company building uh our product with next and

really from my perspective that's that's very much where I am I'm a user of maps someone who values all the uh things that it has to offer because I've I've used them and and so what I'm really excited about and maybe most excited about thinking about what Veet makes possible is it makes possible a lot of amazing things from a user point of view not least it's speed and a few more of course that will get a chance to talk about today

if you haven't come across next then uh maybe it's worth a brief introduction next is a progressive full stack framework for building web applications and what I mean by saying that it's a progressive framework is that it comes with a lot of things out of the box so you you really don't need to know a lot about how things work under the hood to get going everything should work well they should have best practice built in it should be performant should enable all kinds of

things that you might want to do from generating static sites to uh sites without any JavaScript at all to doing SSR to having great SEO interaction to enabling deployment to serverless functions or node servers or GitHub Pages or the point is next is designed to make a lot of things really simple out of the box and as easy as possible so you don't need to

configure anything no matter how complex it might be to do that and normally but the idea of it being a progressive framework is that things very much are within your control to configure so you can actually take as much control of Knox as you would like and that's something that's been true from the early days of next um there's been a hooks mechanism and a way for users not just to configure it within their own project but actually to publish packages modules that enable

other people to benefit from that as well if you want to check it out do go to modules.netjs.org you'll see some of the many modules that have been built by lots of contributors over the years the modules ecosystem is a great great wonderful thing that I'm constantly uh really glad exists and you can see ways of integrating that with cms's deployment targets languages component libraries whatever you might

imagine so next is is a progressive framework it's um has lots of great things to start with and it can be extended hugely and we're powered by Veet webpack's also an option I I should say in in Knox 3 but it's by default and for good reason one of the key things that I want to highlight uh too particularly um one of the the key things is that Veet enables rapid development for us so