Next.js 13 (App Router) Storefront with GraphQL & TypeScript (Part 1)

Let's build a fully-featured e-commerce storefront in Next.js 13 using the App Router paradigm along with GraphQL, TypeScript and Tailwind CSS.
Join me on this adventure and follow the progress via the KZbin videos.
#nextjs #ecommerce #react

[@LarsEjaas]

We do not "like" what you do: We absolutely love it 😍 Keep up the good work guys! Would love to get a better understanding on how to handle GraphQL without a client like eg. Apollo. Something like mutations and lazy queries (eg. like load more functionality) would be great. Thanks again for the awesome video!

[@RobertWildling]

Hey! Zaiste is back! Great to see/hear you again!

[@raideez]

Great content. I will definetely check the whole video later.

[@stevenbaron358]

Hello there! I'm new to Saleor and I'm really enjoying these videos. Thank you so much for creating them and please continue to keep up the great work!

[@augustoeduardo209]

Nice zaiste, miss you

[@AdamJenkinsEverything]

I wish I could give more than one thumbs up! Great stuff. And I actually really value the minor digressions here and there because I learn a little extra along the way. Much appreciated, keep it up!

[@joshuajourneys]

Yeah, Shadcn UI is awsome!

[@SamirElias-ru1td]

amazing content!!

[@user-nw2zu1hx9l]

I was in search of a solution for the App Router, and it appears that this could be beneficial. Thank you for your assistance. Additionally, I'm curious about the AI technology you are utilizing.

[@pawel_890]

Maybe you can add something more interesting than raw fetch for Graphql calls?

[@zaisteprogramming]

Yes, that's the plan and this video is just an introduction. We are about to make it much more complex in the next episodes. The general idea is that with this new paradigm in Next.js 13 (i.e. App Router), you may not need a typical GraphQL client at all (sic!).

[@pawel_890]

@@zaisteprogramming Super, I an looking forward to the next episodes. I learned a lot from your videos and typeofweb.

[@falucho582]

@@zaisteprogramming thanks for such a thoughtful approach. I'm really thankful for and appreciative of your effort. Could you please elaborate a bit more on your last paragraph? "... you may not need a typical GraphQL client at all?" What you think is the best way/tooling/strategy to organize/orchestrate multiple query/mutation requests from a heavily interactive UI to a (backend) graphql-yoga server with multiple endpoints?