The Nuxt big thing in web development?

Nuxt3, an SSR framework for Vue, just hit release candidate last week. Let's take a first look at its most powerful features and compare it to other fullstack JavaScript frameworks like Next.js and Remix.
#webdev #js #TheCodeReport
🔗 Resources
- Nuxt3 Release nuxtjs.org/announcements/nuxt...
- Nuxt Docs v3.nuxtjs.org/getting-started...
- Vue in 100 Seconds • Vue.js Explained in 10...
- Next in 100 Seconds • Next.js in 100 Seconds...
🔥 Get More Content - Upgrade to PRO
Upgrade to Fireship PRO at fireship.io/pro
Use code lORhwXd2 for 25% off your first payment.
🎨 My Editor Settings
- Atom One Dark
- vscode-icons
- Fira Code Font
🔖 Topics Covered
- Nuxt version 3 first look
- Nuxt3 Review
- Nuxt.js vs Next.js
- Server side rendering with Vue.js
- Nuxt.js features overview
- Deploy vue to serverless edge functions

[@mattinpjs]

Nuxt looks really interesting. I'd love to see another video going into even more depth on it

[@alexwilkinsgames]

"Give me a tutorial of {{ nuxt3 }} or give me death" -That Guy who Died

[@__entro]

Same it’d be awesome to see a whole series dedicated to Nuxt 3

[@yaboihawley]

Same 🙌

[@QtheCoder]

Yep need to add updated nuxt content for us vue guys 😂🙏

[@aryanmn1569]

it would be a great idea for nuxt video

[@ErmandDurro]

I have used Nuxt before, and really excited to see the version 3 bringing even more awesome features. Would love to see a full in-depth tutorial from Fireship 😀

[@DevPandaSuraj]

I made a video just like Jeff : kzbin.info/www/bejne/j6OpdpR7mL6li5Y

[@MichaelJClegg]

Same here

[@vikash-kumar-gupta]

Yes please!!

[@_WyreZ]

Yes please!

[@MikeWaltman]

Anthony Fu, who is part of the Nuxt core team, is an Open Source legend. The Auto Imports are from repos he maintains. - unplugin-auto-import - unplugin-vue-components

[@hope-ag]

His Vitesse(vue starter template) project is really great

[@vaaski]

vueuse also rocks, really worth sponsoring that guy

[@miclgael]

Unocss is very cool too!

[@s4ndeep1203]

i believe Legend is the correct word to describe him indeed.

[@IxMeTutorials]

The sindresorhus of the Vue ecosystem :P

[@CodeWithSahand]

I will use it for my nuxt project

[@thothtrismegistus929]

i would like to know if svelte still performs better than vue/react

[@TheGargalon]

@@thothtrismegistus929 I don't think people use svelte because of performance

[@geoAriton]

but what about the Next one after that?

[@danvilela]

@@thothtrismegistus929 They perform the same, the difference is in bundle size

[@thothtrismegistus929]

@@danvilela do you have some benchmarks?

[@RavMucha]

Auto imports should be a feature everywhere. ❤️ Imagine that commit in an Angular project: "Adding auto imports, imports cleanup" +12 additions -2458 deletions.

[@riddixdan5572]

dunno, in big projects the name collision could be a huge headache. I can already imagine something like this happening UserClientsTableHeaderCellFilterContainer

[@RavMucha]

@@riddixdan5572 well, that's just life in this field. Every solution causes a problem elsewhere. 😅

[@riddixdan5572]

@@RavMucha yeah thats true but, tbh, in this case, I don't even see the import issue as a problem, IDE does the auto import for me and keeps it collapsed, out of sight, out of mind, and eslint orders it, if there is a need for it.

[@CarKiller92]

Idk if it's just me but I totally don't mind the imports, especially with name collisions or some naming similarities.. really useful to see if the function I want to use is actually imported from the lib I want instead of something totally different (happens a lot in our project). I also don't really care about the big block of import at the start of the file.. if you are coding, you won't look up there, if you are searching for something, you will ctrl+f anyway.

[@RavMucha]

@@riddixdan5572 well, in that case it might be, but I've seen import hell more than once. Either taking over a project after people that were trigger happy and decided to import everything that could ever be used in an Angular project, or dealing with very badly documented component imports from an obscure UI Framework that was client enforced... There's a lot of scenarios in which my life would be much improved if I could just ignore the imports part.

[@div0ky]

Fireship Pro member here and I'd love to see a full Nuxt 3 tutorial! We're running 3 internal apps on Nuxt 2 and need to know what I'm missing, how to upgrade or change, etc.

[@dputra]

That apifetch function is really interesting. It's rare to see one that implement refresh that way. And that strongly typed api, that's really awesome

[@cameronpaczek5686]

Apollo vue composable basically has the exact same thing for gql its really cool

[@Wilpsn]

both swr and react-query have that, they call it mutate

[@kevinwilliam3163]

@@Wilpsn Yup

[@alexradu1921]

Is it similar to GraphQL?

[@MoreSlater]

and so is the component autoimport magic.. x2

[@griffin955]

Now that my company is looking to implement SSR and Nuxt into our Vue codebase, this video has been fantastic to help understand their justification for being so pressing about getting it added in in 2023. Those auto-imports look to be absolutely clutch. Thanks!

[@themesong5477]

CODE REPORT should get a blog. Petition!

[@WallaceThiago]

Signed by Autumn

[@flamakespark]

Signed by 🔥flamake spark🔥

[@mikopiko]

Signed by John from tennessee

[@aminegdoura4909]

I agree

[@comradeyeet3522]

signed by the president

[@cybershadow3476]

Looks awesome. A 10 minute video on this would be great.

[@crbon770]

Yes please

[@cody_codes]

A full Nuxt 3 tutorial would be awesome! Thanks for putting this video together, I've been stoked about Nuxt v3 for a while now and it's so great to see it's finally reached RC status. Keep up the great work on these videos, I love your content! :)

[@LeviWhalen]

I love seeing all the positive feedback on the Nuxt 3 features! I’ve been a Nuxt user for over four years and it’s awesome to see how far the framework has come.

[@yovan2373]

K0k

[@atinux]

Thank you ❤

[@mtgshmoopy]

The entire time I was watching this video I was thinking "wait.... it can't actually be that easy??" I'd love another video going more in depth on things like pulling in styles and third party components.

[@charlesm.2604]

What do you mean styles ? You have global stylesheets and each component can receive a scoped tag. Vite supports pre-processors so you have access to PostCSS, SASS, etc... 3rd party libraries are the ugly part of Vue 3 since a lot of librairies aren't compatible anymore and the community isn't updating them fast as of yet. Basically you'll start Vue 3 with an immature ecosystem. But you don't really need one to begin with, this isn't the "library" React devs are used to, it's a battery included framework.

[@NoNameAtAll2]

hi no name

[@Im_Ninooo]

a deep dive into this would be awesome! this looks incredible

[@lukemckenna]

Full Nuxt walkthrough would be amazing. It feels very much like an evolution, removing so much redundant actions.

[@youen5567]

I didn't know Nuxt v3 brought so many amazing features. The components being available everywhere is so nice. I used nuxt 2 and would love to see a full tutorial on the V3 from you

[@lardylu]

Love this code report! A full Nuxt3 tutorial would be awesome to get a better understanding of all these new features.

[@borjinator]

I would like to see a tutorial. The auto import thing reminds me of how Swift handles imports.

[@jakeedgar3076]

Definitely would love a full tutorial. Especially with regards to the state mechanism in Nuxt.js thanks for the great video!

[@gregherrick4013]

Thanks for the overview. Awesome! I'd love to see another video (or more) going through the framework! Thanks again.

[@benediktwalch1605]

That sounds really awesome, like the combination of the best parts of some JavaScript frameworks with tons of improvement on top.

[@nullpointerexception3108]

As usual, really nice video. You never disappoint. Nuxt looks really awesome. A more in depth tutorial for Nuxt, would be a nice idea for the nuxt video on your channel.

[@its.arjun.s]

Really want this to be a full video! Vue is a really good framework, and nuxt sounds incredible.

[@xemu3267]

A full nuxt 3 tutorial would be awesome!. Thank you for making this video, I've never heard of nuxt before but now my interest is peaked !

[@ruriko1237]

love the code report, wouldn't mind getting every 2-3 days

[@heyyvishal1]

I believe web community is obsessed with "creating new frameworks", What we really need is just a framework which creates frameworks so every single developer can create their own framework and call it supreme. Booom 💥

[@zb2747]

Yoooo lol this 🔥

[@brodriguez11000]

Call the framework...lumber. The developers are called...lumberjacks.

[@keokawasaki7833]

and now we are building frameworks recursively

[@zxcq]

I must say most new framework are in some way better than what we had. Frameworks become easier to use and work faster.

[@SosaiOyama]

Code is a language. Saying you know English means you can write a poem or write mathematical statements. I agree with you that we should slow down on “hot new frameworks” but part of the constant evolution of language is to adapt. Sort of like if music was MVC and our taste/experiences shape frameworks we write songs in

[@mahitmehta9620]

I can’t wait for hybrid rendering! It is one of my favorite features of next.js

[@JACOBTL23]

The documentation looks super awesome! Might have to use it with my next project

[@DK-ox7ze]

After seeing this, I am actually feeling more depressed than excited. The list of "next mind blowing framework" in front-end development never stops.

[@heroe1486]

Tbh honest it's not a new Framework, it's just Next's equivalent to VueJS, although one could argue Vue is already a framework and is more opinionated than bare React/CRA ootb. But yeah one should really stay away from the new shiny thing syndrome

[@matiascoco99]

@@heroe1486 Agree. Just one thing, nuxt its really taking things to a new level. The idea of the autoimports and the simplicity of the ssr is just astonishing

[@fdg6935]

Nuxt is not new

[@samuelmorkbednarzkepler]

I personally dont get why a lot of people feel this way. Yeah, the front end world has constant iteration and new cool things come out all the time... thats great. Thats how it should be. The opposite would be horrible. A stagnant never changing ecosystem is what makes me feel depressed. Cause thats an actual sign that our code sucks and nobody is doign anything important in this space

[@DK-ox7ze]

@@samuelmorkbednarzkepler There's a difference between never changing vs evolving vs changing like crazy. Plus, there's nothing you can do with one framework that can't do with another.

[@cindrmon]

im rly excited for when nuxt3 releases! keep it up, and im waiting for a full nuxt3 tutorial as well!

[@BrockBelmonte]

Always great videos. I would love to see a full Nuxt tutorial. Keep up the amazing work!

[@planetoftheweb]

Wow. The auto import feature is something I hope every other framework adopts. It seems like all of the good ideas get adopted when one frameworks does something like Hydration. I'm all for letting the computers do more of the work. SSR looks fantastic. The only thing is the horse race is getting more and more complicated. I want to use the way Svelte or maybe even Astro do certain things. Do you see the auto import making it to other platforms?

[@joaomatos1420]

I'm a bit skeptic about maintainability of auto-imports. It's what keeps me from getting into e.g. rails. A system where you don't really know where things come from is... scary.

[@igorswies5913]

@@joaomatos1420 right click go to definition

[@pastuh]

Meh normal IDE imports and you can see that.

[@raz0229]

Never thought of auto imports as a feature. Do people really run into issues with imports?

[@shapelessed]

@@joaomatos1420 Maybe that's a bad idea, but I've seen an approach that lets you import components notmally, or use global ones, stored in a specific folder without imports with a prefix, like

[@johnvandenberg1448]

Really cool stuff! Would love to see a full blown tutorial about this

[@branchyapple]

Awesome video! Would love a longer video 😃

[@the_shua]

DUDE - great summary. We have been using Nuxtjs for healthcare platforms we have built since mid v1. v3 has been eagerly anticipated. Please do a longer form video on Nuxt3 - it has truly been a game changer for us :)

[@StuckDuck]

Nuxt's so nice :) I got to try it out for little time but I definitely wouldn't think twice about using it if I needed Vue for a project.

[@glennmatsiwe8705]

Thank you Jeff it would be nice if you do a full tutorial on nuxtjs 3, i have been using v2 for most of my project huge scale projects so it would be nice also if you could indicate the major differences btween v2 and v3

[@KaizenCodes]

Thanks for releasing this. I have been making Nuxt videos for ages trying to show the awesomeness.. Not stopping now :)

[@rutgercap]

Just started with Nuxt, a full video would be very helpful! This video was very handy already!

[@luismpcunha]

Good video as always, I'd like to see a comparison between this and what other frameworks, such as angular, already provide (besides auto import ofc 🙂)

[@Alex-sv8th]

Auto Import was already available on Nuxt 2, you just had to set it up

[@sammatuba4366]

Wow, this is exciting. Looking forward to your Nuxt3 tutorial!

[@icesplendent2899]

I would be really happy to see another video talking more about nuxt!!

[@n0xter95]

I'll put this nuxt to the list of frameworks I know, thanks to your 100 seconds videos series

[@Steel0079]

Well said.

[@torkilddyvikolsen2063]

On larger projects I feel most of this is better covered with Vite and plugins, a robust microservice backend/custom API, and a cloud based deployment infrastructure (love edge delivery btw). But I'm glad this is getting released, as configuration is tricky and there are many scenarios where you'd want the ease of use Nuxt 3 seems to be able to provide. Yes please on a more in-depth rundown!

[@FreedomForKashmir]

I was thinking about this auto import feature in react just yesterday and here you are with this video

[@nicolasguillenc]

I like that you don’t seem too biased when explaining new tools, like diminishing nuxt features bc you like next or something like that

[@JamesGaehring]

Please a deeper dive on Nuxt! I recently upgraded a sizable Vue 2 project to Vue 3, and while differences don't seem that big on the changelog, I am realizing just how much of a game-changer Vue 3 is once you start working with it and lean into the ergonomics. And seeing how Nuxt3 is really capitalizing on that makes me eager to play around with it more.

[@cd1655]

I would really like an in-depth tutorial. I've used Nuxt2 for a long time now and have a deep understanding of it. The problem with Nuxt3 is the documentation isn't fully complete and it leaves some questions.

[@NeverCodeAlone]

Very good overview and into. It helps me a lot!!

[@sagiajaj17]

Great summarization, as always! I would love to see a full nuxt3 tutorial

[@youssefmansour5756]

we really need a tutorial from you please!

[@Kairulol]

At work I currently have an application in Nuxt 2, while using the Vue composition API and via plugins. I’ve tried to upgrade it to Nuxt 3 but the big issue is that the Apollo GraphQL module hasn’t been updated yet. I’ve already gone through over a hundred files removing composition-api imports, I’d need to do it again to rewrite Vuex code into Pinia and convert any FontAwesome icon usage away from the Nuxt module and into the standard Vue plugin or CSS route. Sure we could just use the Vue plugins for non-updated modules, but that almost defeats the point of using Nuxt. We fell in love with Nuxt this time last year, but the upgrade path from 2 to 3 (or even Bridge) just makes us wish we had gone with a barebones Vue 3 setup. Great video though, would love to see the both the Vue and Nuxt ecosystems grow, god knows they need it after being fragmented between Vue 2 and 3 for so long.

[@daheck81]

The Nuxt team mentions that a migration from 2 to 3 should be avoided until stable release which is expected in June. The main migration guide is still a work in progress and Nuxt 3 is a complete rewrite so it is expectable that a lot of modules will not work out of the box. You shouldn't blindly migrate to the newest things in general without evaluating the advantages and costs for it. We just use Nuxt for our marketing sites and will wait for the stable release and its core modules (like image, content etc) to be compatible as well (all documented on their roadmap) before we even consider starting to migrate

[@jannispfeiffer5457]

I am working with a colleague on a rather simple single page application and only got to realize how amazing Nuxt really is. I would totally love a full video

[@ChristopherAtwood96]

I've been waiting for release for so long! Can't wait to start using it

[@AByteOfPi]

When I have time, I'm definitively gonna learn vue. At that moment, a full Nuxt tutorial could be preeety useful. Great video man, keep up the good work!

[@esgn.design]

I'm loving Vue, you'll not regret to learn it!

[@sumitsapkota3792]

Auto import is great but can cause to write long components name to reduce name collision which can be Hectic. And As a nextjs ❤️ developer file based routing and ssr already making my life easy Though nuxt looks cool 😎

[@ojvribeiro]

Maybe you can avoid name collision by nesting components in directories like /components/Navbar/List.vue. Then use it like this:

[@Thunder007de]

Thanks for the video. Would appriciate a full length tutorial!

[@MrShentov]

This looks awesome! Please do continue!

[@kendedetar]

Oh helly yeah! I’ve been a little disappointed with the Vue ecosystem sincs the switch to Vue 3 (it’s been rough), so seeng nuxt as a well developed framework that guides you along the way, that sounds awesome! I’d really like to see a full tutorial ot Nuxt3 😄

[@tycooperaow]

Same! It's motivating me to double down on Vue with Nuxt

[@samuelmorkbednarzkepler]

I personally think Vue 3 is not just the best improvment I have seen for Vue in a long while but probably the most impressive improvment I have seen happen to any of the major frameworks in my entire career as a frontend coder. Just for the record. So people dont think its generally accepted that vue 3 was a bad improvment. Cause its not. Its super really not

[@kendedetar]

@@samuelmorkbednarzkepler Agreed. But a lot of libraries were missing long after its release, documentation wasn’t the best, and the overall feel of the ecosystem has not been as complete as react for example. I love Vue, and would like to see it thrive, but the transition to vue 3 has been hard. Hopefully a lot of devs will try out Nuxt3 and new libraries will emerge to work with Vue 3.

[@samuelmorkbednarzkepler]

@@kendedetar I had some trouble right at the start, but that was before Vue 3 was officially out. Vue 3 was acutally not the recomended option until just a few months ago exactly because lots of parts of the ecosystem was lagging behind, most notable vues own library for state management, and the docs needed work. But I would say that, in the last 9 months at least, I have not had any issues with Vue 3 at all. Its been a great experience. Except maybe the docs being outdated, but that all changed like a month or two ago when they just released the new docs and now thats all great again also. The only vue 2 spesific libraries that still lags behind are usually UI component libraries like vuetify. Which I think are still working on their Vue 3 version. But I dont really like UI component libraries myself to be honest so that never bothered me in the first place. Plus Vue 3 composables have opened up a world for much more usefull Vue libraries like VueUse to exist. So the new libraries to Vue I find to actually be a lot more usefull than the old vue 2 ecosystems libraries. For this reason, and almost just off of VueUse alone(which is a great library), I actually feel like the ecosystem for vue is better with vue 3 than it ever was with vue 2 even despite lots of libraries lagging behind to this day. But yeah, if you really like UI component libraries than I guess I can see how it doesnt feel that way. Or maybe theres some other vue 2 spesific libraries I dont know about. To be honest, I try to stay away from framework spesific libraries in general.

[@peter042]

Szia! Szerinted SvelteKitet vagy Nuxt3-at használjak?

[@lilbigman9127]

Tutorial please!! This looks really useful and I'd love to know how easy it is to implement within existing or ongoing projects

[@charlesm.2604]

Docs

[@barrybadgerneth14]

Was waiting for this before embarking on my own personal project. Can not wait for the full release, they're doing gods work over there.

[@moneeral-dakkak9267]

WE NEED THAT TUTORIAL Thanks for the effort your channel is really amazing 👏🏻

[@ManasMadrecha]

All it needs is the update of Content V2 (within a month), and Nuxt will reclaim its position as the best option for easy, fast, and feature-rich web development and documentation. 😋

[@nishitshetty1746]

Just curious - what are the costs associated with this framework? I do understand the hassle of imports, however, whenever I review a code the imports lists my dependencies which is good to know sometimes. Do you think we can generate the list of imports in nuxt?

[@blvckbytes7329]

They have to be stored in some kind of dependency graph, so yeah, they're easy to just print to the screen. But I just don't get why people have to abstract to such a high degree... What's next, build a full app by only typing 5 lines? It's already easy enough, we don't need yet another framework to make it "easier". That's what happens when computers get powerful enough and the really smart people have bootstrapped a layer of abstraction that now everybody can work with and abstract further. Then we get a clusterf*** like this. Ugh, sry for the rant.

[@MaulikParmar210]

Cost : Ever changing framework every few months that you have to maintain is the real hidden cost. There are no LTS releases which would give you timeframe to manage and upgrade projects in pre determined manner along with prefixed guides to migrate major versions in more maintainable manner, small things adds up quickly when you are working on complex projects that can't be SPA anymore. Though mostly these frameworks are intended to be used by small scale projects and not to be used by team of developers having separate concerns about part of their application, it would affect such cases less than those who does that, so answer would be : It depends on your use case. Though no successful project relies on single technology, it's always mixture of best abilities of each :) Edit : Realised you were talking about "framework" of importing, that's just another way of allowing autowiring or namespace discovery they are doing to reduce importing boilerplate which usually can be done automatically via properly configured editor or ide. Ultimately it doesn't matter much to experienced dev who knows what he or she is doi ng.

[@Mabi19]

For reviewing component and composable dependencies - no, at least not that I know of, but those are the only things that are auto-imported. You still need to import all external libraries. Composable and component imports are usually not that important, as long as you review the basic implementation of the component you're looking at; you can also look at the component/composable dependencies manually if you so desire (imports wouldn't make this that much easier)

[@JulienRoyCode]

YES, I want a full tutorial, this looks amazing!!!

[@david_awad]

would also love a more full tutorial on this! thanks for doing it.

[@ukaszszarpak1938]

I have significant experience with Nuxt2 and I can tell you that most of the times the framework works the way you expect it to, but when it doesn't it's hella pain in the neck to overwrite the default settings. Nuxt2 has let me down a couple of times already, so even though Nuxt3 seems like a great choice for your next web app, please don't let the hype influence your choice, but rather build something small with it, experiment with some edge cases and then decide if that's a right fit for you. Auto imports seem like a bugs' nest.

[@ethannr1]

agreed, I find the documentation quite poor when problems happen

[@moon_bandage]

I'm very sceptical about auto imports, I'm curious to know what others think about it. To me it feels like it "solves" a minor inconvenience, and introduces a whole slew of small issues. Like refactoring. If you update a file name, most IDEs will offer you an option to automatically update import strings across your project. Naming collisions are also an issue. Honestly I don't mind importing at all, I think it's good to see what has been included from the outside into your file all in a single place, it's maintainable and clear. I currently work on projects where the bundle size is a very small concern, and we still opt to import components instead of registering them globally, because I don't think global registering is a clear way to go about it. And auto imports feel like global registration...

[@samuelmorkbednarzkepler]

I personally think the concerns you mentioned are minor conserns that wont cause me more issues then a warning every now and again while the "minor" inconvencince as you described it of having to write a bunch of import statments every time I want to make a new component is actually not a minor inconvenience at all. Its a massive inconvenience. Ultimatley I would much rather spend 1 min fixing a naming colition once or twice per project then spend an 5 minutes writing import statments every time I write a new component only to then spend the rest of the time with the project having to scroll past 24 lines of import statements every time I want to find the actual code in the component. Having this be auto importet sounds like a massive increase in my development speed and code readability. By reducing code clutter my stamina for coding long hours probably also increases. Also it will liley make me a better coder too because I might make me more willing to modularise my code. This just because I dont have to struggle with the mental hassle of thinking "oh. boy. I should probably make this into a seperate component but the thought of mentally having to sort out all the import statments is bumming me out right now so id rather just say fuck it and continue to put that off for a while." Which is something that actualyl happens quite often. I saw the same thing happen when Vue released the composition API. Because there was much less lines of code I had to write upfront to make a new component I found myself being much more willing to write new components since it was less of a mental hurtdle to do so. I think auto imports probably achievethe same effect. The less effort I have to make in order to organize my code the more often will I end up atually doing so when Im working. Espesially when im already tired.

[@moon_bandage]

@@samuelmorkbednarzkepler That's fair I respect that, programming is a lot more a social and personal preference influenced than people make it out to be. (Not aimed at you specifically) For example a lot of people like that Python doesn't have curly braces, I personally think it hurts readability pretty bad for instance. As for imports, they're always collapsed for me, so I don't scroll over them, and my auto completion finds most of my imports, so that's why I enjoy the benefits they bring, being able to see what is actually defined from the outside, or right clicking and checking out their file. There's more factors than development speed for me, it's about maintain ability and clarity, and imports provide that for me, but I would argue also for my team. Auto import, to me, seems like registering globally so you don't need to import, and globally imported stuff in my experience, spawns a wild growth of not knowing where something is defined and naming collisions. But to each their own! I see this feature is opt-in so every team can decide themselves what they prefer in the end. I say for prototyping and small apps this is definitely the way to go

[@samuelmorkbednarzkepler]

@finance what problems did you have?

[@RR-zd5yt]

I've been using Vuetify which has its own loader that auto register Vuetify components globally. Together with Vue's global component registration mechanism, it's a tradeoff between dealing of using import solutions provided by a framework versus handling import of every component by yourself. Personally, the former gives more convenience, but I can see that clarity is important, too.

[@moon_bandage]

@konqi I knew this would tick off some python enthusiasts haha, you picked quite the example, yes that is definitely a real world use case :p! With sufficient nesting and many lines on each block, I personally think it becomes hard to see which blocks were "closed" down the line, especially if you go multiple indentations back/in. Let's just say I think the opening syntax doesn't add much, but the closing syntax definitely helps readability, for me at least. I agree for small code it's all fine. In fact I prefer to use Stylus as my css preprocessor because it gets rid of curly braces and any other excessive symbols. But I don't think this extends over to programming, styling is very different and way simpler (basically a handful of Key:value that's it). But as I mentioned in one of the replies, programming is far more personal preferences and social when looking at small stuff like auto imports or curly braces. But I do think curly braces hold a lot of ground given most newly made programming languages still use them, or something like them (like end in julia, elixir). They have the option not to, they're often compiled languages and can easily assert, but they choose not to do so for readability

[@tojeiro_me]

It just looks awesome. A full tutorial would be great 🙂 can’t wait for the stable release, but already want to dive in.

[@StevenBenjamin]

Yes please, I would love a full Nuxt tutorial. - Thanks for all your hard work.

[@bobuccman1424]

i would love to see a 100secs vid about nim

[@Fireship]

That will happen eventually

[@dailymeow3283]

Nim what's nim lol

[@whoman7930]

I like how they implemented api routes for different http methods. I wish nextjs also implements that.

[@evanparrish4329]

Nice overview! I'd also love to see a longer tutorial

[@fabrizionastri9484]

Looks amazing ! Looking forward to the Nuxt Tutorial

[@bradhaupt1261]

Super interesting, I’ve just started using Vue a few months ago and this sounds great! Would this work with something like capacitor to make iOS apps?

[@calimio6]

It seems possible with a custom plugin.

[@amiruladli8057]

yeap, if nuxt3 allow us to work painlessly with capacitor, our life will complete, I already built an app using nuxt2 but most of UI library wants vue3, now I'm stuck in limbo waiting for nuxt 3

[@calimio6]

@@amiruladli8057 you can already use nuxt3. The core is ready and pretty much stable

[@jawngee]

I went from Next to Nuxt and had a really hard time going back to Next for a different client project. There's a lot of great DX in Nuxt (and Vue tbh).

[@jacquesduplessis6175]

Yeah, I agree.... I went from Nuxt to Next, and it wasn't as good🤦🏻‍♂️

[@NZIsaacNZ]

big disagree

[@khaki32]

@@NZIsaacNZ Why?

[@remyfamily8652]

I've really enjoyed using NextJS. I tried learning Vue but I don't like how the page is templated. Vue has some really great things like a redux type state management but you can get away without using that for most things. I truly like the way React handles it's components in regards to layout.

[@fdg6935]

Are you using nuxt 3 ? If yes, are you using it for production?

[@ftamas88]

Definietly would love to see a full tutorial on Nuxt, looks promising!

[@alexwhb122]

So cool! looking forward to trying this out.

[@barj]

I really need to learn web development at some point. I'm putting it off because If I watch enough code reviews I might pick it up.

[@strifeclient]

Big fan, I definitely agree that you should learn, it’s an awesome experience worth experiencing. I’ve personally worked with both React and Vue. Both great options, but my preferred choice is Vue, so Nuxt 3 is something I can’t wait to start using. Good luck on learning and I hope to see some progress update videos on your channel! Cya 👋

[@TomNotThomasZA]

This is literally me

[@BrendansReasons]

Full Nuxt tutorial vote count! 👇

[@trueGOLG]

Thank you so much for the wonderful videos. It could be great to see the Nuxt course.

[@khundkarujairulislam4302]

yes a full tutorial would be nice! Thanks!

[@vn0ir]

Approach Nuxt with caution. If you are considering adopting it for production I would suggest building a pretty detailed test case first. I’ve developed a full multilingual booking management system on a previous version of Nuxt. It seems super approachable at first (it is, the first few weeks are lovely) and you get started so quickly! The issue is the edge cases. As soon as you get near the edges of its capabilities you will find that lovely documentation abruptly stops and you will spend all your days sorting through other peoples spaghetti to try and do basic things. I did our next project in React. Sure there is a slower start and less ‘magic’ but in the end less ‘magic’ means less undocumented spaghetti.

[@AustinMarlar]

We had the exact same issue. I think Nuxt and Next work for certain types of projects but they haven't been the projects I've been working on. All of the "magic" is great until it isn't...

[@themule137]

This 'magic' is what simultaneously attracts me to and then turns me off of Rails for Ruby

[@virinom]

Fuck the rest, this is the best :D. As a PHP developer, finally I can move into the JS world with Nuxt. I fell in love.

[@eskTea]

sweet summary, and a full Nuxt tutorial would be sick

[@ScriptureFirst]

Thank you for this. Excellently broken down

[@matthewaxisa6058]

There are some interesting features here which I really like the look of, but as someone who has a lot of Vue 3 experience, I think a lot of the features which are being sold as Nuxt features in this video are just Vue 3 features. I am aware the Jeff mostly has experience with React but I think for anyone new to Vue ecosystem, they should check out the base framework first (especially for small/medium projects). I would love to see more Vue content on this channel but maybe focus on the core framework first! :P

[@ChamplooMusashi]

Auto importing is an anti-feature that hinders readability. "What files does the current module depend on?" Is a question answered directly by the first part of a js file. It's almost a contract saying "if you know about the following imported functions then you can read this file fine". It can even be a hint when fixing a bug, optimizing, etc. I can see how it "could be" convenient but I'd prefer the inconvenience of spending 20s or so managing imports on my own (espescially when linters and other tools further simplify this process)

[@1dosstx]

FYI you can still explicitly import items if you want to do it like that. I was anti-auto import too, but the more I use it the more I prefer it.

[@ChamplooMusashi]

@@1dosstx the problem is that it's a default behaivor meaning that it doesnt really matter what my preference is, I have to follow whatever the project has declared is their style. Also, I looked on the extension store for vsc to see if there was some nuxt plugin to show imports for a file somehow but that didnt seem to be supported by any I saw at a glance. The functionality I described would be critical for me to work in this ecosystem

[@martinlategan]

Yes please! Looking forward to the in depth tutorial 🤟

[@veecks]

Bro, I want this tutorial so badly, nice video!

[@tntg5]

It is amazing to see how much effort is put into creating new frameworks which require a substantial effort to learn, as opposed to making existing ones better. There is almost a new framework every week.. I can't keep up

[@rumplstiltztinkerstein]

Meanwhile the bigger corporations are still using old java

[@IvanRandomDude]

@@rumplstiltztinkerstein I am sure rewriting millions of lines of critical backend code is good reason enough to stay there

[@rumplstiltztinkerstein]

@@IvanRandomDude slowly rewriting libraries in a more effective language like rust can be considered an investment. It will be a lot cheaper to maintain in the long run. Plus a lot safer.

[@ankitsanghi]

I’ll be honest I think imports are a good thing. At least that way you know where things are coming from. With no imports a new person working on the code will have no idea where anything is or where things are coming from. It becomes difficult to differentiate between built in components and newly made ones

[@TheMitchingHour]

I agree. I so often scroll to the top of the file just to click through to the file in VSCode.

[@asandax6]

Easy fix would be to allow adding the imports to the top of the file if so desired so any one taking a look at the code and wants imports can just use a command or button in an IDE and imports are added.

[@danvilela]

No bro, the auto imports is only for pre defined folders (like components). It really helps. For every other thing you need to import. In other words, you always knows where it comes from.

[@nikilragav]

F12 tho

[@Nounearthlyglow]

Would comments at the top work?

[@mel-182]

See on the nuxt one!! Will be waiting for full tutorial!

[@Idleness76]

It would be great to see more in depth information. Very interested!

[@StephenMoreira]

Been on the Angular/NestJS for a long time. Nuxt is probably the first that seems really sweet to me for a long time. I've used auto imports in another platform though for about 4 years now, I personally don't like it; too much magic going on under the hood and you lose a lot of quick visibility when opening up files. For example when I open an angular component or service I can quickly know what files are being used in that component, overall architecture, how I might make thing's more modular going forward etc etc; with files that everything is just auto imported you have to dig into the file to see what is actually being used and kinda hold it in your head how you might split up responsibility of files, etc etc.

[@7heMech]

Bro... That's so awesome, also the auto-imports should be a default js feature 😭

[@AJ23mady]

No it definitely shouldn't be

[@adamneon]

Yes please! A full nuxt3 tutorial would be amazing!

[@Skasix00]

Interesting!! Hope a new video is made, really excited to know more about NUXT :D

[@TehGaema]

The auto import might be a deal breaker for me. In really large enterprise applications this could be a huge pain. I also found it interesting that a lot of the functions appear like React hooks. Overall it looks like a great framework and I do believe you could move fast building with it, but if given the choice between Nuxt and Next - I’m choosing Next every time.

[@syropian]

FWIW you can continue to import manually and things will still work - I think you might be able to turn the feature off entirely if you want.

[@svenyboyyt2304]

You can turn it off. But if naming conflicts are an issue, you are probably naming things wrong. And also what is the reason you would choose Next? You didn't say.