very clear demo and explanation, I always use asyncData and nuxtServerInit to render page in server side, and using vuex for component to get the data, but using fetch for dynamic fetching is also cool, just need to add a loading spinner or skeleton screen to make the waiting pleasant and enjoyable !!!
So easy now - which I know I’ve read before - but sinks in with this video (thanks!) - asyncData for pages, fetch for components. In my app, I have a bunch of page that are the same regardless of guest/subscriber - I’ll use async for that. And then for those subscriber premium components that lay in all the goodness, I’ll use fetch for those...thanks!
thanks I won't. But I lost my voice this week so you might have t wait til next week. However I did create this free course which got published yesterday - explorers.netlify.com/learn/get-started-with-nuxt
Thanks a lot for this video, have been strugglinh 4 hrs yesterday to find a way how to redirect from fetch method, now seems I will have to stick to asyncData
Hi! I have a question, which one is better, fetch anything I need on a page using asyncData method and pass all the information to the components via props (or using the vuex store) or delegate the fetch action (using fetch method) to the components and make them fetch the information that they need? I hope you understand me! Anyway, great videos!
it depends on what you want. there is no right or wrong way. do you want the user to go to an error page if nothing returned - then use asyncData. do you have various api calls on a page such as blog posts and comments then fetch works better cause if comments api fails you can still see posts. or you can use asyncData to get posts from api and fetch to get the comments. hope that helps
Coming soon! I promise. however if you are in a hurry I have some courses on vue school on it - vueschool.io/courses/vue-apollo-graphql-fundamentals vueschool.io/courses/learn-graphql-fundamentals
very clear demo and explanation, I always use asyncData and nuxtServerInit to render page in server side, and using vuex for component to get the data, but using fetch for dynamic fetching is also cool, just need to add a loading spinner or skeleton screen to make the waiting pleasant and enjoyable !!!
thanks for the nice feedback as always Stephen
Thanks for the videos, you're a life saver.
Glad to help
So easy now - which I know I’ve read before - but sinks in with this video (thanks!) - asyncData for pages, fetch for components.
In my app, I have a bunch of page that are the same regardless of guest/subscriber - I’ll use async for that. And then for those subscriber premium components that lay in all the goodness, I’ll use fetch for those...thanks!
glad it was of help 🥰
very nice explanation. you cleared my confusion Mam. Thanks a lot.
Glad to hear that :)
love your voice
why thank you :)
@@DebbieOBrien it reminds me good things
Great explanation!!!!! Want more!!!!!!!
thanks, glad you liked it
Tysm
continue to make more content don't stop
_/\_
thanks I won't. But I lost my voice this week so you might have t wait til next week. However I did create this free course which got published yesterday - explorers.netlify.com/learn/get-started-with-nuxt
@@DebbieOBrien recover fast💪💪💪
Thanks a lot for this video, have been strugglinh 4 hrs yesterday to find a way how to redirect from fetch method, now seems I will have to stick to asyncData
Glad it helped
Thank you! 🙌🏻
You are so welcome!
Hi! I have a question, which one is better, fetch anything I need on a page using asyncData method and pass all the information to the components via props (or using the vuex store) or delegate the fetch action (using fetch method) to the components and make them fetch the information that they need? I hope you understand me!
Anyway, great videos!
same here. following this one =)
it depends on what you want. there is no right or wrong way. do you want the user to go to an error page if nothing returned - then use asyncData. do you have various api calls on a page such as blog posts and comments then fetch works better cause if comments api fails you can still see posts. or you can use asyncData to get posts from api and fetch to get the comments. hope that helps
what is the rest of that line of code under your photo? const mountains = await $axios.$....
not sure without watching it back but all demos can be found here - nuxtjs.org/examples/data-fetching/async-data
This tutorials are awesome! I'd like to learn more about vue-apollo and graphql if it's something you want to do
Coming soon! I promise. however if you are in a hurry I have some courses on vue school on it - vueschool.io/courses/vue-apollo-graphql-fundamentals
vueschool.io/courses/learn-graphql-fundamentals
could you share the sources? :)
most of the content is from the nuxt docs examples
nuxtjs.org/examples/data-fetching-async-data