UPDATE: The Interview is out @ ruclips.net/video/33ex2A04b7g/видео.html PS: Today is your last chance to leave questions for Evan with regards to his new company - VoidZero. Check it out at ruclips.net/user/postUgkxJwWXI0yI2TpP2OqV7JX084zqi4KOuvmO 👍🏻
One thing I liked in "Next" version more is the code organization. Specifically the fact that components, that are intended to be used on a specific page are lying closer to that page. And it's me, who actually never used React/Next and always uses Vue/Nuxt. :) I'm really missing an ability to organize code logically when I'm using Nuxt. Putting every component into a global space is not the best ogranization, don't you agree? I tried to invent some "workaround" like duplicating pages hierarchy under the "components" dir and other approaches, but all of them not convenient to work with comparing to organizing code "by features" as opposed to "by types", where you need to jump back and forth between several global folders over and over again even if you are working on a single specific feature at the moment.
I see your point! In think this is mainly solved by layers on a bigger scope, but I think there is space for a more fine-grained solution. Follow this discussions which suggests to bring that feature to Nuxt! Follow github.com/nuxt/nuxt/issues/28894 along.
Amazing. Any plans for a video about auth options for Nuxt projects? I have been looking at different solutions: auth utils Better-auth sidebase/auth Lucia (Deprecated) nuxt-auth (Nuxt 2 only)
Supabase is pretty good, but there’s so many variables. If you need a DB supabase nigh unbeatable, managed I like both Logto and Kinde, and auth-utils if you want to dip your toes into creating it yourself
How is it possible to contribute to the Nuxt ecosystem as a Product Designer? It is shame that nuxt is so criminally underrated and I am here to help change this!
The documentation can be improved. A lot of people seems to have issues with understanding basic Nuxt concepts even though, they are explained currently in Nuxt documentation. What is also missing are guides that describe the usage of multiple tools for one problem e.g. Nuxt + Nitro + H3. Nuxt docs usually only link to the other libraries or modules.
First think that most Nextjs user really dislike from nuxt is they way the name things. like NuxtLink, NuxtLayout, NuxSomething, NuxtAnotyherThing, (not to mention defineNuxtRouteMiddleware which i believe is better tobe defineMiddleware). Why dont they just name it Link, Something.. Its like american version of English where they need more explanation to something. The second one is the hell of confusion between module and plugin. everytime i decide to learn nuxt, when it comes to module and plugins, i rethink my decision and get back to nextjs. or mybe there is not much resource on the internet talks about these two.
The crap with modules sucks, additionally the thing that then you don't explicitly import something from 'somewhere' but instead have access to the stuff automagically what is stupid.
One-Word components are not really a things Vue to avoid collision with future HTML components! Plugins vs modules: * Plugins are Runtime * Modules are build time. Might consider a video on that!
@@TheAlexLichter in that case it's still the problem, as with auto imports. My concern is that if I install library for push notifications, I would like to use it `import {usePush} from 'my-library-of-choice'. Like in `normal` javascript ecosystem. Disabling autoimports according to docs `This will disable auto-imports completely but it's still possible to use explicit imports from #imports.` won't let me to `import something 'my-library-of-choice'` but `import {something from '#imports'` that is even worse.
@@najlepszyinformatyk1661 Stop whining. If you prefer configuration over convention, explicit vs "magic", then just continue using nextjs. This is like Laravel vs Symphony. You can achieve the same with both, it just depends on your coding style preference. Do you want to code faster by leaning towards the framework's conventions (and the cons that it brings)? Use Laravel. Do you want to configure and architect your apps manually, spend time writing boilerplate code before starting to write your business logic? Use Symphony.
![Stromae, Pomme - “Ma Meilleure Ennemie” (from Arcane Season 2) [Official Visualizer]](http://i.ytimg.com/vi/1F3OGIFnW1k/mqdefault.jpg)
![[#2024MAMA] G-DRAGON - 무제(Untitled, 2014)+POWER+HOME SWEET HOME+뱅뱅뱅+FANTASTIC BABY | Mnet 241123 방송](http://i.ytimg.com/vi/Ox29z5Nf1Uk/mqdefault.jpg)
UPDATE: The Interview is out @ ruclips.net/video/33ex2A04b7g/видео.html
PS: Today is your last chance to leave questions for Evan with regards to his new company - VoidZero.
Check it out at ruclips.net/user/postUgkxJwWXI0yI2TpP2OqV7JX084zqi4KOuvmO 👍🏻
As a react dev, this video is amazing to get a first look into how vue works in a non-tutorial scenario. Thank u
Glad it was helpful! 😊
i tend to forget how nice is the vue api vs react. Nice video.
Please make beginners to advanced Nuxt js course with project ( A real-world project )
Have you checked out the Mastering Nuxt course by Michael Thiessen? Not free. But worth its money.
Great content. It's always awesome to see how different developers solve the same problems.
Can never get over how Nuxt & Vue looks, and is, sooooo much nicer to work with compared to Next & React 👌🏽
Converting Next app to Nuxt ❤🔥I HAVE to see this one!
One thing I liked in "Next" version more is the code organization. Specifically the fact that components, that are intended to be used on a specific page are lying closer to that page. And it's me, who actually never used React/Next and always uses Vue/Nuxt. :)
I'm really missing an ability to organize code logically when I'm using Nuxt. Putting every component into a global space is not the best ogranization, don't you agree? I tried to invent some "workaround" like duplicating pages hierarchy under the "components" dir and other approaches, but all of them not convenient to work with comparing to organizing code "by features" as opposed to "by types", where you need to jump back and forth between several global folders over and over again even if you are working on a single specific feature at the moment.
I see your point! In think this is mainly solved by layers on a bigger scope, but I think there is space for a more fine-grained solution. Follow this discussions which suggests to bring that feature to Nuxt! Follow github.com/nuxt/nuxt/issues/28894 along.
we need that hat merch !! xD
Lol, too funny. You tell'em. They are always ghosting Vue/Nuxt
No joke, I’ve never heard Theo even mention Nuxt lol
He tends to more nowadays
Amazing. Any plans for a video about auth options for Nuxt projects? I have been looking at different solutions:
auth utils
Better-auth
sidebase/auth
Lucia (Deprecated)
nuxt-auth (Nuxt 2 only)
Lucia is not deprecated?
Lucia will be deprecated early next year. See eg x.com/pilcrowonpaper/status/1843258855280742481?s=46&t=tJveHCYtiY5v-kdgTMClJQ
Auth is on the list but sadly always a very tricky topic to teach due to the sheer options, different setups etc etc
Supabase is pretty good, but there’s so many variables. If you need a DB supabase nigh unbeatable, managed I like both Logto and Kinde, and auth-utils if you want to dip your toes into creating it yourself
@@TheAlexLichter thank you. Very sad to me. Was it not one of the best ones? Maybe even the best
Would love to see a video about nuxt and storybook.
great video, thank you
You are welcome! ☺️
Nice video Alex. please which extension or shortcut are you using to create the vue component?
I think it's a custom keyboard vscode shortcut, pretty easy to do, I have my owns too
@@rapha-v That's cool. Thank you!
like it!
Epic and It is Very FUNNY
Amazing.
YES PLEASE
How is it possible to contribute to the Nuxt ecosystem as a Product Designer? It is shame that nuxt is so criminally underrated and I am here to help change this!
The documentation can be improved. A lot of people seems to have issues with understanding basic Nuxt concepts even though, they are explained currently in Nuxt documentation. What is also missing are guides that describe the usage of multiple tools for one problem e.g. Nuxt + Nitro + H3. Nuxt docs usually only link to the other libraries or modules.
Why you have all code in app folder, in default nuxt project everything is main folder. How to change it to app?
He is using upcoming nuxt 4 folder structure
I explained all about the new folder structure in this video 👌🏻
ruclips.net/video/KnCNOp5Pbfs/видео.html
Kommentar für den Algo
Danke! 🙏🏻
How to migrate Nuxt2 to Nuxt3 in one hour? )))))))))
epic
First think that most Nextjs user really dislike from nuxt is they way the name things. like NuxtLink, NuxtLayout, NuxSomething, NuxtAnotyherThing, (not to mention defineNuxtRouteMiddleware which i believe is better tobe defineMiddleware). Why dont they just name it Link, Something.. Its like american version of English where they need more explanation to something. The second one is the hell of confusion between module and plugin. everytime i decide to learn nuxt, when it comes to module and plugins, i rethink my decision and get back to nextjs. or mybe there is not much resource on the internet talks about these two.
The crap with modules sucks, additionally the thing that then you don't explicitly import something from 'somewhere' but instead have access to the stuff automagically what is stupid.
One-Word components are not really a things Vue to avoid collision with future HTML components!
Plugins vs modules:
* Plugins are Runtime
* Modules are build time.
Might consider a video on that!
Re auto imports: you can disable them but using them sparingly should help 👌🏻
@@TheAlexLichter in that case it's still the problem, as with auto imports. My concern is that if I install library for push notifications, I would like to use it `import {usePush} from 'my-library-of-choice'. Like in `normal` javascript ecosystem. Disabling autoimports according to docs `This will disable auto-imports completely but it's still possible to use explicit imports from #imports.` won't let me to `import something 'my-library-of-choice'` but `import {something from '#imports'` that is even worse.
@@najlepszyinformatyk1661 Stop whining. If you prefer configuration over convention, explicit vs "magic", then just continue using nextjs.
This is like Laravel vs Symphony. You can achieve the same with both, it just depends on your coding style preference.
Do you want to code faster by leaning towards the framework's conventions (and the cons that it brings)? Use Laravel.
Do you want to configure and architect your apps manually, spend time writing boilerplate code before starting to write your business logic? Use Symphony.
You're about to receive a very harsh email from theo
no react without vue
😂❤
Amazing.