When Vue3 came to scene many devs started putting pressure on Nuxt team. I believe Daniel was a newcomer to the team at that time if I am not mistaken. He was really proactive and helped many people who were not sure what to do and how to migrate (I believe he worked on Nuxt Bridge first) and made a composition api module for Nuxt. I still appreciate the work of the other team member but this guy gave me a feeling that I can trust Nuxt in the future. And here we are now with a stable version and all the amazing features (plus Nitro and unjs of course).
yes! change the default folder structure! honestly it seemed so cool in the beginning but it really doesn't scale beyond small-ish examples. an `src` or `app` folder is great and i generally divide by domains but i'd be open to other ideas as long as it's still customizable
I totaly agree that ! Folder structure is just a nightmare and not customizable for complex routes. You have to do many trick things like hooks for complex routes
LoL The moose story, it was like a horror movie where the generator dies and someone has to go start it and be put in danger but instead of a masked evil soul, it was a moose that was to be feared LMAO
🎯 Key Takeaways for quick navigation: 00:14 *🚀 Introduction to Nuxt.js development* - Daniel Roe introduces Nuxt.js as the backend for boot Dev. - Nuxt.js initially started as a server-side rendering template but evolved into a framework. - Daniel joined the Nuxt.js team around version three and later became the lead maintainer. 01:54 *🌟 Daniel's journey and leadership in Nuxt.js* - Daniel's transition from building startups to contributing to Nuxt.js. - The process of rewriting Nuxt.js from scratch for version three. - Daniel's role as the lead maintainer of Nuxt.js and the team dynamics. 02:36 *🛠️ Daniel's role as a full-time open source maintainer* - Daniel's responsibilities as a full-time open source maintainer. - Other projects Daniel is involved in, such as Elk and being on the core team of Magic Rex and Fontaine. - The unique privilege and challenges of being a full-time open source maintainer. 03:45 *🦌 The elk project and Daniel's interest in animals* - Elk project as a Mastodon client and its unique concept. - Discussion on moose and elk, highlighting the differences in size and behavior. - How Daniel's interest in animals and projects like Elk intersects with technology. 07:43 *🔄 Openness and avoiding vendor lock-in in Nuxt.js* - Nuxt.js core value: Avoiding vendor lock-in and providing deployment flexibility. - Support for various deployment providers like Cloud workers, Azure static web apps, Netlify, and Vercel. - Daniel's philosophy on openness, allowing users to make choices based on their needs. 11:01 *🚢 Comparing deployment flexibility in Nuxt.js and Next.js* - Addressing criticisms of vendor lock-in in Next.js and Vercel. - Nuxt.js commitment to deployment flexibility and support for various providers. - Encouraging users to choose deployment providers based on their preferences and needs. 13:08 *🚚 Smooth migration experience from Vue 3 SPA to Nuxt.js* - Transitioning from a Vue 3 SPA to Nuxt.js for improved SEO and performance. - The seamless migration experience, ensuring up-to-date dependencies. - Gratitude for the Nuxt.js team's effort and the benefits of moving away from SPA architecture. 14:33 *🔄 Evolution and rationale behind auto-importing in Nuxt.js* - Auto-importing as part of Nuxt.js's move from a monolithic to a composable framework. - The challenge of balancing functionality options with minimal build impact. - The broader context of composability and options in Nuxt.js version 3. 17:32 *🧩 Auto Imports in Nuxt.js* - Auto Imports in Nuxt.js simplify code writing by handling imports automatically. - Benefits include effortless logic writing, tree shaking advantages, and the option to disable if preferred. 22:11 *🚀 Improving Page Loading and Prefetching* - Nuxt.js aims to be interactive as soon as possible, preloading chunks for linked pages in the background. - Tools like PageSpeed Insights may misinterpret this, so manual prefetch control is available using the `no-prefetch` option on `n-link`. - Balancing page speed scores with actual user experience is essential, and prefetching can enhance overall site snappiness. 26:31 *🕵️♂️ Probing Frameworks for Answers* - Starting a podcast, inviting framework maintainers, and directly asking questions is an effective approach to understanding and resolving framework-related queries. - It allows for nuanced discussions, dispelling doubts, and gaining insights from the experts. 29:27 *🌐 Use Cases of Nuxt.js* - Nuxt.js is versatile, supporting various use cases, including back-end-for-front-end (BFF) patterns. - It caters to building full-stack applications or client-side-rendered apps, providing flexibility for different project needs. - The framework's evolution, introducing more features like a first-class database integration, aims to expand its range of use cases. 32:43 *🛠️ Balancing Control and Flexibility* - Nuxt.js strives to strike a balance between flexibility and maintainability. - Designing options that offer users full control without compromising maintenance is crucial. - Active community involvement, reporting issues, and providing fixes contribute to a framework's adaptability and success. 35:19 *🚀 Static Site Generation in Hugo* - Static site generated with Hugo, a static site generator. - No JavaScript on the site, fully generated at compile time. - Discussion on the possibility of using Next.js for both static and interactive web app needs. 36:02 *🔄 Handling JavaScript for Blog Pages* - Addressing the challenge of users being signed out on the blog. - Proposal to turn off JavaScript for blog pages and inject a custom JavaScript snippet. - Brief overview of the steps involved, including root rules and middleware. 37:38 *🧩 Updating Head Tags in Vue3* - Difficulty in updating head tags in a Vue3 app compared to the index.html file in Vue2. - Discussion on using the `useHead` reactive function for managing head tags. - Mention of upcoming improvements in Next.js for handling third-party scripts using `n scripts`. 39:32 *🛠️ Simplifying Script Handling with `n scripts`* - Introduction of the upcoming `n scripts` functionality. - Aimed at providing better ways to handle third-party scripts and improve site performance. - Collaboration with the Google Aurora team and others for best practices. 42:32 *🏷️ Caution on Google Tag Manager* - Discussion on the drawbacks and risks of using Google Tag Manager. - Comparison to giving customer service representatives database access. - Emphasis on the need for developer oversight and training when using such powerful tools. 46:23 *🔄 TypeScript Typing in Next.js* - Favorite feature in Next.js: TypeScript typing for strong type support. - Enjoyment of the typing flow from the server to the front end. - Positive impact on reducing bugs and enhancing the development experience. 49:49 *🎮 Inspiration behind Boot.dev* - Origin of Boot.dev as an educational platform for backend development in Python and Go. - Focus on computer science fundamentals. - Incorporation of gamification elements to create an engaging learning experience. 52:37 *🎮 Teaching Coding Gamification* - Coding is inherently gamified, making work enjoyable. - University experiences sometimes strip away the gamified nature of coding. - Importance of connecting coding theory to real-world applications. 56:22 *📁 Changing Next.js Folder Structure* - Proposed restructuring of Next.js projects for better organization. - Benefits of having a dedicated source directory. - Improved performance by optimizing file system scanning. 59:22 *🔄 Balancing Server and Client Concerns* - Addressing concerns about frameworks like Nuxt.js and Next.js blending server and client code. - Clear mental model: distinguish between server API and view parts. - Emphasizing the importance of separating sensitive server-side logic from client-side code. Made with HARPA AI
![[#2024MAMA] G-DRAGON - 무제(Untitled, 2014)+POWER+HOME SWEET HOME+뱅뱅뱅+FANTASTIC BABY | Mnet 241123 방송](http://i.ytimg.com/vi/Ox29z5Nf1Uk/mqdefault.jpg)
the extent of 'this guy knows what hes talking about' makes me want to try nuxt
he does, true
When Vue3 came to scene many devs started putting pressure on Nuxt team. I believe Daniel was a newcomer to the team at that time if I am not mistaken. He was really proactive and helped many people who were not sure what to do and how to migrate (I believe he worked on Nuxt Bridge first) and made a composition api module for Nuxt. I still appreciate the work of the other team member but this guy gave me a feeling that I can trust Nuxt in the future. And here we are now with a stable version and all the amazing features (plus Nitro and unjs of course).
Right!?
The focus of Nuxt giving you the flexibility to do what you want while taking away the maintenance burden was a breath of fresh air!
yes! change the default folder structure! honestly it seemed so cool in the beginning but it really doesn't scale beyond small-ish examples. an `src` or `app` folder is great and i generally divide by domains but i'd be open to other ideas as long as it's still customizable
Try out Nuxt layers
We have a quite big project in the company I work, the default works just fine.
@@Remeroska Nuxt Layers is so good!
I totaly agree that !
Folder structure is just a nightmare and not customizable for complex routes. You have to do many trick things like hooks for complex routes
Nuxt is better than Next... React alone makes this statement true
🔥🔥🔥
LoL The moose story, it was like a horror movie where the generator dies and someone has to go start it and be put in danger but instead of a masked evil soul, it was a moose that was to be feared LMAO
🎯 Key Takeaways for quick navigation:
00:14 *🚀 Introduction to Nuxt.js development*
- Daniel Roe introduces Nuxt.js as the backend for boot Dev.
- Nuxt.js initially started as a server-side rendering template but evolved into a framework.
- Daniel joined the Nuxt.js team around version three and later became the lead maintainer.
01:54 *🌟 Daniel's journey and leadership in Nuxt.js*
- Daniel's transition from building startups to contributing to Nuxt.js.
- The process of rewriting Nuxt.js from scratch for version three.
- Daniel's role as the lead maintainer of Nuxt.js and the team dynamics.
02:36 *🛠️ Daniel's role as a full-time open source maintainer*
- Daniel's responsibilities as a full-time open source maintainer.
- Other projects Daniel is involved in, such as Elk and being on the core team of Magic Rex and Fontaine.
- The unique privilege and challenges of being a full-time open source maintainer.
03:45 *🦌 The elk project and Daniel's interest in animals*
- Elk project as a Mastodon client and its unique concept.
- Discussion on moose and elk, highlighting the differences in size and behavior.
- How Daniel's interest in animals and projects like Elk intersects with technology.
07:43 *🔄 Openness and avoiding vendor lock-in in Nuxt.js*
- Nuxt.js core value: Avoiding vendor lock-in and providing deployment flexibility.
- Support for various deployment providers like Cloud workers, Azure static web apps, Netlify, and Vercel.
- Daniel's philosophy on openness, allowing users to make choices based on their needs.
11:01 *🚢 Comparing deployment flexibility in Nuxt.js and Next.js*
- Addressing criticisms of vendor lock-in in Next.js and Vercel.
- Nuxt.js commitment to deployment flexibility and support for various providers.
- Encouraging users to choose deployment providers based on their preferences and needs.
13:08 *🚚 Smooth migration experience from Vue 3 SPA to Nuxt.js*
- Transitioning from a Vue 3 SPA to Nuxt.js for improved SEO and performance.
- The seamless migration experience, ensuring up-to-date dependencies.
- Gratitude for the Nuxt.js team's effort and the benefits of moving away from SPA architecture.
14:33 *🔄 Evolution and rationale behind auto-importing in Nuxt.js*
- Auto-importing as part of Nuxt.js's move from a monolithic to a composable framework.
- The challenge of balancing functionality options with minimal build impact.
- The broader context of composability and options in Nuxt.js version 3.
17:32 *🧩 Auto Imports in Nuxt.js*
- Auto Imports in Nuxt.js simplify code writing by handling imports automatically.
- Benefits include effortless logic writing, tree shaking advantages, and the option to disable if preferred.
22:11 *🚀 Improving Page Loading and Prefetching*
- Nuxt.js aims to be interactive as soon as possible, preloading chunks for linked pages in the background.
- Tools like PageSpeed Insights may misinterpret this, so manual prefetch control is available using the `no-prefetch` option on `n-link`.
- Balancing page speed scores with actual user experience is essential, and prefetching can enhance overall site snappiness.
26:31 *🕵️♂️ Probing Frameworks for Answers*
- Starting a podcast, inviting framework maintainers, and directly asking questions is an effective approach to understanding and resolving framework-related queries.
- It allows for nuanced discussions, dispelling doubts, and gaining insights from the experts.
29:27 *🌐 Use Cases of Nuxt.js*
- Nuxt.js is versatile, supporting various use cases, including back-end-for-front-end (BFF) patterns.
- It caters to building full-stack applications or client-side-rendered apps, providing flexibility for different project needs.
- The framework's evolution, introducing more features like a first-class database integration, aims to expand its range of use cases.
32:43 *🛠️ Balancing Control and Flexibility*
- Nuxt.js strives to strike a balance between flexibility and maintainability.
- Designing options that offer users full control without compromising maintenance is crucial.
- Active community involvement, reporting issues, and providing fixes contribute to a framework's adaptability and success.
35:19 *🚀 Static Site Generation in Hugo*
- Static site generated with Hugo, a static site generator.
- No JavaScript on the site, fully generated at compile time.
- Discussion on the possibility of using Next.js for both static and interactive web app needs.
36:02 *🔄 Handling JavaScript for Blog Pages*
- Addressing the challenge of users being signed out on the blog.
- Proposal to turn off JavaScript for blog pages and inject a custom JavaScript snippet.
- Brief overview of the steps involved, including root rules and middleware.
37:38 *🧩 Updating Head Tags in Vue3*
- Difficulty in updating head tags in a Vue3 app compared to the index.html file in Vue2.
- Discussion on using the `useHead` reactive function for managing head tags.
- Mention of upcoming improvements in Next.js for handling third-party scripts using `n scripts`.
39:32 *🛠️ Simplifying Script Handling with `n scripts`*
- Introduction of the upcoming `n scripts` functionality.
- Aimed at providing better ways to handle third-party scripts and improve site performance.
- Collaboration with the Google Aurora team and others for best practices.
42:32 *🏷️ Caution on Google Tag Manager*
- Discussion on the drawbacks and risks of using Google Tag Manager.
- Comparison to giving customer service representatives database access.
- Emphasis on the need for developer oversight and training when using such powerful tools.
46:23 *🔄 TypeScript Typing in Next.js*
- Favorite feature in Next.js: TypeScript typing for strong type support.
- Enjoyment of the typing flow from the server to the front end.
- Positive impact on reducing bugs and enhancing the development experience.
49:49 *🎮 Inspiration behind Boot.dev*
- Origin of Boot.dev as an educational platform for backend development in Python and Go.
- Focus on computer science fundamentals.
- Incorporation of gamification elements to create an engaging learning experience.
52:37 *🎮 Teaching Coding Gamification*
- Coding is inherently gamified, making work enjoyable.
- University experiences sometimes strip away the gamified nature of coding.
- Importance of connecting coding theory to real-world applications.
56:22 *📁 Changing Next.js Folder Structure*
- Proposed restructuring of Next.js projects for better organization.
- Benefits of having a dedicated source directory.
- Improved performance by optimizing file system scanning.
59:22 *🔄 Balancing Server and Client Concerns*
- Addressing concerns about frameworks like Nuxt.js and Next.js blending server and client code.
- Clear mental model: distinguish between server API and view parts.
- Emphasizing the importance of separating sensitive server-side logic from client-side code.
Made with HARPA AI
Really loved the vendor locked in section. I've so far deployed nuxt to vercel, amplify, netlify and it's so easy.💚
No way, this is a banger ❤
tyty, daniel is awesome
Every time I use Nuxt it crashes and I have to manually reload the the page.
how bout sveltekit?
Banger of an episode
so much tech debt even before starting developing the UI
Vue I think is more popular in Europe and Asia. Even in Japan I am seeing more Vue stuff than React.