Відео

Thanks! Glad you liked it 👍

By the way, if you enjoy learning and want to dive deeper into computer science topics made simple, I run another channel where I summarize key concepts from Tech books. I would be very glad if you subscribe to my new channel: ua-cam.com/channels/ZYhXrFwhFUOXuSQNgfk-Sw.html

@@SakuraDev I subscribed it 👍🏻

Thanks so much! I'm glad you enjoyed the tutorial, and I appreciate your kind words! 💪

By the way, if you enjoy learning and want to dive deeper into computer science topics made simple, I run another channel where I summarize key concepts from Tech books. I would be very glad if you subscribe to my new channel: ua-cam.com/channels/ZYhXrFwhFUOXuSQNgfk-Sw.html

Great observation! 😊 Yes, you’re absolutely right that session management can be fully handled in NestJS. The reason I split it between Next.js and NestJS was mainly for performance optimization and reducing backend calls. By handling cookies in Next.js server actions: ✔️ We reduce unnecessary API requests to NestJS, improving response times. ✔️ It allows better integration with Next.js middleware for SSR/SSG workflows. ✔️ In some cases, it simplifies authentication flows (e.g., checking session validity before making a request to NestJS). That said, centralizing everything in NestJS is also a valid approach, especially if you want strict backend control. Hope that clears it up! Let me know if you’d like a deeper dive into either approach. 🙌

By the way, if you enjoy learning and want to dive deeper into computer science topics made simple, I run another channel where I summarize key concepts from Tech books. I would be very glad if you subscribe to my new channel: ua-cam.com/channels/ZYhXrFwhFUOXuSQNgfk-Sw.html

@@SakuraDev oh yea this makes sense. Thnx for clarification. Also amazing content

Great catch! 🎯 You’re absolutely right that without the .unique() constraint, the database schema allows multiple profiles to reference the same user, effectively making it a one-to-many relationship instead of one-to-one. I’ll double-check the implementation and update it if needed. Thanks for the keen eye and for supporting the channel! 🚀

By the way, if you enjoy learning and want to dive deeper into computer science topics made simple, I run another channel where I summarize key concepts from Tech books. I would be very glad if you subscribe to my new channel: ua-cam.com/channels/ZYhXrFwhFUOXuSQNgfk-Sw.html

Glad to hear it! 👍

Thanks for watching and I'm glad you found it helpful!

By the way, if you enjoy learning and want to dive deeper into computer science topics made simple, I run another channel where I summarize key concepts from Tech books. I would be very glad if you subscribe to my new channel: ua-cam.com/channels/ZYhXrFwhFUOXuSQNgfk-Sw.html

im facing this problem , thanks for you comment

Hey! 👋 Thanks for sharing your solution! This will definitely help others facing the same issue! 🚀 Appreciate you taking the time to share your experience. 🙌

By the way, if you enjoy learning and want to dive deeper into computer science topics made simple, I run another channel where I summarize key concepts from Tech books. I would be very glad if you subscribe to my new channel: ua-cam.com/channels/ZYhXrFwhFUOXuSQNgfk-Sw.html

Great question! 🎯 Keeping roles in the DB ensures real-time accuracy-if a role changes, it's immediately reflected. Storing it in the JWT means users need to re-login to get updated roles. Both approaches have trade-offs! 🚀

By the way, if you enjoy learning and want to dive deeper into computer science topics made simple, I run another channel where I summarize key concepts from Tech books. I would be very glad if you subscribe to my new channel: ua-cam.com/channels/ZYhXrFwhFUOXuSQNgfk-Sw.html

You're welcome! I'm glad it was helpful.

By the way, if you enjoy learning and want to dive deeper into computer science topics made simple, I run another channel where I summarize key concepts from popular tech books. I would be very glad if you subscribe to my new channel: ua-cam.com/channels/ZYhXrFwhFUOXuSQNgfk-Sw.html

Thank you for the kind words! 🙌 I’m glad you find the content helpful. I’ll definitely consider covering those topics in future tutorials. Stay tuned for more! 🚀

By the way, if you enjoy learning and want to dive deeper into computer science topics made simple, I run another channel where I summarize key concepts from Tech books. I would be very glad if you subscribe to my new channel: ua-cam.com/channels/ZYhXrFwhFUOXuSQNgfk-Sw.html

Hi, great question!. The guard that is closer to the function is run first. Because the function is passed as callback to the closet guard and then it returns a new function. The new function is passed to the next closest guard and so on

@@SakuraDev OK thanks. I thought the first decorator was performed at the top until it went down to the last one that is the closest to the function

You're welcome! It's always great to help others with more specialized topics like GraphQL and NestJS.

Happy to help! 🙏

I’m glad you find the content helpful, and I’m excited to share more about GraphQL with you soon!

Thanks so much for the love! ❤️

By the way, if you enjoy learning and want to dive deeper into computer science topics made simple, I run another channel where I summarize key concepts from CS books. I would be very glad if you subscribe to my new channel: ua-cam.com/channels/ZYhXrFwhFUOXuSQNgfk-Sw.html

I'm glad you found it helpful! Testing in NestJS is a crucial topic, and I'll definitely consider adding a video about it in the future.

You're very welcome!

Hi @AGM140580! Great question! 😊 In NestJS, it’s better to import the module that exports the service rather than re-registering it as a provider. This ensures the service remains a singleton (if provided in the root) and follows NestJS's modular architecture. Just make sure the owning module exports the service in its exports array. Thanks for engaging!

I'm glad you found it helpful!

By the way, if you enjoy learning and want to dive deeper into computer science topics made simple, I run another channel where I summarize key concepts from popular programming books. I would be very glad if you subscribe to my new channel: ua-cam.com/channels/ZYhXrFwhFUOXuSQNgfk-Sw.html

Thank you so much 🙏. Hope it was helpful for you.

By the way, if you enjoy learning and want to dive deeper into computer science topics made simple, I run another channel where I summarize key concepts from CS books. I would be very glad if you subscribe to my new channel: ua-cam.com/channels/ZYhXrFwhFUOXuSQNgfk-Sw.html

Thanks

Thanks for your feedback. Hope it was helpful for you!

You're welcome! Hope you found it helpful.

By the way, if you enjoy learning and want to dive deeper into computer science topics made simple, I run another channel where I summarize key concepts from CS books. I would be very glad if you subscribe to my new channel: ua-cam.com/channels/ZYhXrFwhFUOXuSQNgfk-Sw.html

Thank you, Ahmed! I’m glad you found the tutorial helpful. JWT authentication is such an important topic in NestJS, and I’m thrilled it provided you with value.

Yes, you’re absolutely right! Using NestJS to handle cookies directly is often a better approach, as it centralizes logic and avoids unnecessary redirects or exposing sensitive information in searchParams. It’s a cleaner solution, especially in production-level applications. Let me know if you’d like more details or examples!

@@SakuraDev Thank you very much for the answer! You are the best teacher. Please write down a lesson on how to properly process cookies in Nestjs. He really needs him!

Wow, thank you so much for such amazing feedback! 😊 I’m truly honored to hear that you found the video so helpful, even compared to paid courses.

By the way, if you enjoy learning and want to dive deeper into computer science topics made simple, I run another channel where I summarize key concepts from CS books. I would be very glad if you subscribe to my new channel: ua-cam.com/channels/ZYhXrFwhFUOXuSQNgfk-Sw.html

@@SakuraDev Signed! Serious topics. Great content. I will study. I recommend everyone.

Thanks for watching! I'm happy to hear you found it useful. 👍

By the way, if you enjoy learning and want to dive deeper into computer science topics made simple, I run another channel where I summarize key concepts from CS books. I would be very glad if you subscribe to my new channel: ua-cam.com/channels/ZYhXrFwhFUOXuSQNgfk-Sw.html

Thank you so much! 🙏 Hearing that means the world to me.

By the way, if you enjoy learning and want to dive deeper into computer science topics made simple, I run another channel where I summarize key concepts from CS books. I would be very glad if you subscribe to my new channel: ua-cam.com/channels/ZYhXrFwhFUOXuSQNgfk-Sw.html

Nice tip 💯. Thanks for your feedback

Thanks for watching, I'm glad you found it helpful!

Great question, Ahmed! 😊 Nest knows to use the LocalStrategy when you pass 'local' to the AuthGuard because the name 'local' is set in the LocalStrategy class using the @Injectable() decorator, typically through the super({}) call in the constructor of PassportStrategy. This name acts as an identifier, allowing the AuthGuard to link the strategy with the parameter you pass. Thank you for your thoughtful question, and I’m happy to explain further if needed! 🙌

Thanks for the feedback! I'm glad you found the explanation helpful. Thank you so much for support 💖

Thank you for your detailed questions! 😊 Let me address each point:

1- .env Setup in NestJS: Great observation! While .env support can feel more straightforward in some frameworks, NestJS intentionally separates concerns to align with its modular architecture. Using the @nestjs/config package for .env management is considered the standard way in NestJS, providing flexibility and scalability for larger applications. While it may seem like more setup initially, this approach ensures you can easily manage configurations across modules, which is particularly helpful for production-grade applications.

2- ConfigService Usage: You’re absolutely right about the benefits of ConfigService-it abstracts away manual parsing and type conversion, making configuration handling cleaner and more robust. In this project, I chose a more direct approach to show how the system works at a lower level, but I agree that using ConfigService is a better practice for production. I'll make a note to cover this in future videos to highlight the advantages!

3- TypeORM Synchronize: Enabling synchronize in development is helpful because it simplifies schema updates during active development. However, in production, it’s best to disable this and rely on proper migrations to ensure controlled and predictable database changes. You're correct that failing to test migrations thoroughly in a staging environment can lead to bugs in production. Best practice is to rigorously test migrations in a staging environment before deployment.

By the way, if you enjoy learning and want to dive deeper into computer science topics made simple, I run another channel where I summarize key concepts from CS books. I would be very glad if you subscribe to my new channel: ua-cam.com/channels/ZYhXrFwhFUOXuSQNgfk-Sw.html

Thanks for watching, I hope you enjoyed it! Here is the github Link github.com/vahid-nejad/nestjs-graphql-course

By the way, if you enjoy learning and want to dive deeper into computer science topics made simple, I run another channel where I summarize key concepts from CS books. I would be very glad if you subscribe to my new channel: ua-cam.com/channels/ZYhXrFwhFUOXuSQNgfk-Sw.html

@ of course

Thanks for your feedback. Actually, I didn't understand your point. Could you please clarify that?

When you create a module you must make sure that what you create in it only works within it. If you need to use things from module A in module B you must export in "exports" the functionalities or services that you want to provide to other modules; and in "providers" are the services that you provide in your own module. This is called module dependency, when module A depends on module B to work, therefore, module A should only contain in "imports:[ModuleB]" and would have access to all the functionalities of B (obviously when you use the services they will appear to come from the path where they are created, but internally the creation of the classes will be handled by the Dependency Injection Container). //Module A @Module({ imports:[PrismaModule, JwtModule, UserModule], controllers: [AuthController], providers: [AuthService], }) export class AuthModule {} //Module B @Module({ imports:[PrismaModule, JwtModule], controllers: [UserController], providers: [UserService, ], exports:[UserService], }) export class UserModule {}

Thanks for the feedback! 👍

By the way, if you enjoy learning and want to dive deeper into computer science topics made simple, I run another channel where I summarize key concepts from CS books. I would be very glad if you subscribe to my new channel: ua-cam.com/channels/ZYhXrFwhFUOXuSQNgfk-Sw.html