The Nuxt big thing in web development? 

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

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

Same 🙌

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

it would be a great idea for nuxt video

His Vitesse(vue starter template) project is really great

vueuse also rocks, really worth sponsoring that guy

Unocss is very cool too!

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

The sindresorhus of the Vue ecosystem :P

I made a video just like Jeff : ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-YrFEaEcYrU4.html

Same here

Yes please!!

Yes please!

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

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

but what about the Next one after that?

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

@@danvilela do you have some benchmarks?

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

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

@@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.

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.

@@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.

Yes please

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

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

@@Wilpsn Yup

Is it similar to GraphQL?

and so is the component autoimport magic.. x2

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.

hi no name

Signed by Autumn

Signed by 🔥flamake spark🔥

Signed by John from tennessee

I agree

signed by the president

K0k

Thank you ❤

Yoooo lol this 🔥

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

and now we are building frameworks recursively

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

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

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.

@@joaomatos1420 right click go to definition

Meh normal IDE imports and you can see that.

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

@@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

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

@@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

Nuxt is not new

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

@@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.

Well said.

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

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

@@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.

@@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.

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

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

agreed, I find the documentation quite poor when problems happen

The next framework will be...English.

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

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.

@@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

@finance what problems did you have?

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.

@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

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

big disagree

@@NZIsaacNZ Why?

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.

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

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.

@@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

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...

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

That will happen eventually

Nim what's nim lol

Docs

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

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.

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.

F12 tho

Would comments at the top work?

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.

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.

It seems possible with a custom plugin.

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

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

Why would you learn them all? Knowing 1 or 2 extremely well is better than learning 10 and not knowing them enough

@@IvanRandomDude that's a good observation

No it definitely shouldn't be

same

Same