This concept is interesting. I have worked with next 13/14, RSC is amazing. I think every page in nuxt app should be server component by default. Always fetch data on the server/page.
I did and I am. I am an senior frontend engineer in one company and I believe that experimental in frontend is fun to use and can be powerful too. I would never opt-in for experimental features on the backend.
Thanks for covering bleeding edge features, Erik. It would be great if you could go more in depth with mini-app of server components. I still can't understand why you don't need a server, maybe you could clarify this point in greater detail?
any idea if there's a way to server render a component on which a prop depends on head's metadata (i.e. color mode) on a single line? I've been creating a ref with a deafult value and then setting the one I need within the onNuxtReady hook, which works, but seems like unnecessary wiring, it's the only way I found to pre-render a component (so it's not loaded after the main content) without getting hydration mismatch errors that break the interactivity with the component. Edit: didn't notice that you mentioned it in the video. The onNuxtReady hook works as a workaround for those cases. Some interactive components stop propagating the props when the mismatch happens so they'll need it.
![[ ออกกอง ] วัยหนุ่ม 2544 โลกหลังลูกกรง..ทัวร์กองถ่ายหนังใน "คุกของจริง" | JUSTดูIT.](http://i.ytimg.com/vi/vB--aOkZCpw/mqdefault.jpg)
thanks for always releasing the good content on nuxt/vue!
This concept is interesting. I have worked with next 13/14, RSC is amazing. I think every page in nuxt app should be server component by default. Always fetch data on the server/page.
Love your Nuxt videos. And this was something I never understood but heard about a lot, so great topic choice! Thanks a ton.
Great topic. I must admit that I was hoping for some "live" coding examples and not pp presentation. But you did a good coverage.
Amazing video, Erik! Hope you make more videos about Nuxt 3 with live coding in the future :)
I did and I am. I am an senior frontend engineer in one company and I believe that experimental in frontend is fun to use and can be powerful too.
I would never opt-in for experimental features on the backend.
thanks for the update!
Thanks for covering bleeding edge features, Erik. It would be great if you could go more in depth with mini-app of server components. I still can't understand why you don't need a server, maybe you could clarify this point in greater detail?
Ok very weird question, what font are using for your slides? It looks really slick 😂
Have used Suspense in Production on Vue.
any idea if there's a way to server render a component on which a prop depends on head's metadata (i.e. color mode) on a single line? I've been creating a ref with a deafult value and then setting the one I need within the onNuxtReady hook, which works, but seems like unnecessary wiring, it's the only way I found to pre-render a component (so it's not loaded after the main content) without getting hydration mismatch errors that break the interactivity with the component.
Edit: didn't notice that you mentioned it in the video. The onNuxtReady hook works as a workaround for those cases. Some interactive components stop propagating the props when the mismatch happens so they'll need it.
How is the lazy prop similar/different from LazyUserProfile?
I believe it's very similar.
I knew the react shit would splash everywhere
I don't get it u say that u don't have interactivty in nsc ,and u use ref inside it?
You can't have a ref inside of it.
@@ProgramWithErik17:25 and what did you do here i'm confused sorry 😅
Suspense is still experimental yet Nuxt use it in the core lol
And there is nothing wrong with that.
Would not be first time using experimental features man :D
great for SEO.. wait.. isnt SSG literally punished by Google? .. cant crawl that good... or do i have misinformation....
Ssg seems like it would be the best for SEO
Хорош 👍