In this comprehensive tutorial, we'll take you through the exciting world of building modern web applications using Next.js 13.x and GraphQL. Whether you're a seasoned developer or just starting out, this tutorial will provide you with the knowledge and hands-on experience you need to create powerful and dynamic web applications. 🔗 **Tutorial Files and Resources:** Before we dive in, make sure you have the necessary resources handy: - Download the starter code and final project files from [GitHub Repository Link]. - Explore the live demo of the project at [Demo Link]. 📚 **What You'll Learn:** Here's a sneak peek of what we'll cover in this tutorial: - Setting up your development environment with Node.js and npm/yarn. - Creating a Next.js project from scratch and understanding its core concepts. - Introducing GraphQL and its benefits for modern application development. - Building a full-stack application with Next.js on the front end and GraphQL on the back end. - Setting up Apollo Client for seamless communication between the front end and back end. - Designing dynamic UI components using Next.js's powerful features. - Implementing GraphQL queries and mutations to fetch and manipulate data. - Integrating advanced features like authentication and pagination. - Deploying your Next.js and GraphQL application to production-ready platforms.
I have a question that how can we create a resolver with validation in Prisma so that we can get the error? Like if the user already exisxt any such error while doing mutation then how to write it and how to show the error on the frontend??
Hi, I have one question: Does making the provider component a client component affect SSR? Basically, would everything work like a React application, not like a Next.js application? Please correct me if I'm wrong. Thanks!
Sir your channel has lot of content,As a Beginner I am unable to understand where to start.Please Make Video on how to use/guided way to learn full stack web development from your channel
If you can reply this comment when you finish it so I see it.. I have subscribed as well.. please when do you estimate it being done .. and what is the swiggly clone
The way you are using API folder in the pages folder is the Next12 approach , can't we do it in 13 approach by putting it in the app folder? By the way great source of inspiration you are
its both way possible in 13.x if you use app dir then place things there ..otherwise all goes in pages, while we create next app using cli it asks for all such options
![Felix "Unfair" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/Oswujxm2Ag0/mqdefault.jpg)
In this comprehensive tutorial, we'll take you through the exciting world of building modern web applications using Next.js 13.x and GraphQL. Whether you're a seasoned developer or just starting out, this tutorial will provide you with the knowledge and hands-on experience you need to create powerful and dynamic web applications.
🔗 **Tutorial Files and Resources:**
Before we dive in, make sure you have the necessary resources handy:
- Download the starter code and final project files from [GitHub Repository Link].
- Explore the live demo of the project at [Demo Link].
📚 **What You'll Learn:**
Here's a sneak peek of what we'll cover in this tutorial:
- Setting up your development environment with Node.js and npm/yarn.
- Creating a Next.js project from scratch and understanding its core concepts.
- Introducing GraphQL and its benefits for modern application development.
- Building a full-stack application with Next.js on the front end and GraphQL on the back end.
- Setting up Apollo Client for seamless communication between the front end and back end.
- Designing dynamic UI components using Next.js's powerful features.
- Implementing GraphQL queries and mutations to fetch and manipulate data.
- Integrating advanced features like authentication and pagination.
- Deploying your Next.js and GraphQL application to production-ready platforms.
I have a question that how can we create a resolver with validation in Prisma so that we can get the error? Like if the user already exisxt any such error while doing mutation then how to write it and how to show the error on the frontend??
Hi, I have one question: Does making the provider component a client component affect SSR? Basically, would everything work like a React application, not like a Next.js application? Please correct me if I'm wrong. Thanks!
Straight to the point
Sir your channel has lot of content,As a Beginner I am unable to understand where to start.Please Make Video on how to use/guided way to learn full stack web development from your channel
ruclips.net/video/7eC2Pcna0Ak/видео.html
Can you make a video with subscriptions with next js you can use a Google map library and then show real time changes in location on multiple clients
will add in swiggy clone nextjs
If you can reply this comment when you finish it so I see it.. I have subscribed as well.. please when do you estimate it being done .. and what is the swiggly clone
github.com/tkssharma/t3-stack-monorepo/tree/develop/apps/nextjs13-with-graphql
The way you are using API folder in the pages folder is the Next12 approach , can't we do it in 13 approach by putting it in the app folder? By the way great source of inspiration you are
its both way possible in 13.x if you use app dir then place things there ..otherwise all goes in pages, while we create next app using cli it asks for all such options
@@tkssharmamay i know whats the different anyway? like component if i put in app dir?
U are awesome 🎉🎉🎉🎉🎉🎉
Please pass this message to others too :)
thanks ,, helpful video
you forgot to add the link to the repo
github.com/tkssharma/t3-stack-monorepo/tree/develop/apps/nextjs13-with-graphql
so messy. schemas dont even make sense
github.com/tkssharma/t3-stack-monorepo/tree/develop/apps/nextjs13-with-graphql