Do You Really Need React Query || An Architectural Overview

[@CodeInDraw]

Brother U literally explained it amazingly, brother one request please keep going, stay motivated brother. I personally need this kinda informative session, and I wish I can see you daily or on consecutive days. But I want your videos brother ❤

[@tapasadhikary]

Hey, thank you! Yeah trying my best to keep doing… hoping the channel to grow as well 🙌❤️

[@raihanchowdhury295]

I have watched 10min of it . I appreciate your hard work! 🎉

[@tapasadhikary]

Thanks for watching… ❤️. What happened to the rest? 😃

[@emilia1520]

This was such a good video! Truly a gem! ❤

[@tapasadhikary]

Thank you!

[@mahdirafi6537]

excellent explanations dada❤

[@tapasadhikary]

Thanks a ton ❤️

[@mahdirafi6537]

@@tapasadhikary welcome dada

[@anandagharami8957]

Absolutely loved this video! from kolkata. The way you broke down the concepts was incredibly clear and insightful. I've been wondering about the necessity of using React Redux in my projects. Could you please make a video on 'Do You Really Need React Redux? .Keep up the fantastic work!

[@tapasadhikary]

@@anandagharami8957 thank you, and great suggestion

[@luner_lynx]

Thanks for sharing knowledge.

[@tapasadhikary]

Most welcome

[@rafeuddaraj]

dada, you have explained this "React Query" very well. I am also learning English by watching your videos. Tapas da you are really a good teacher take my love dada. If you have a request, you will discuss "Web Socket" in detail if you have time.

[@tapasadhikary]

So nice of you! Keep learning bro… I'm starting my Friday live on both English and Bangla… we will discuss a lot of cool topics there too ❤️

[@rog0079]

great video! i have a question, lets say i have a nextjs app, for authentication i have created a server function getServerSession to fetch token from cookies & check validity, it is fine on the server, but what would be the best way to implement/pass auth token throughout client components? Context api, React query? What would be the best practice? Thanks!

[@tapasadhikary]

Context API. Why? Because of its availability at once and usage in places.. You might have the use cases of setting it back too, example logout.. So can take care in context itself. react-query I would use for pointed data and their usages only. Also, if you use providers from next-auth, it provides the session information to both client and server using APIs.

[@sajjadmugdho662]

This Video is gem for me.

[@tapasadhikary]

❤️❤️

[@ronydas5474]

Great

[@arijitdas31]

Dada can you make an updated react playlist or atleast make a video highlighting which topics are still relevant and which have become redundant due to react 19 and react compiler

[@tapasadhikary]

@@arijitdas31 actually all the core concepts in the react playlist will still be relevant in react 19, a few things like ref, context api will have major changes, but to understand them you need to know the background and that's where existing lessons will come in handy. I am making a video on React 19(the first video of the React 19 series) where I shall mention about it. That video will come the end of this week.

[@arijitdas31]

@@tapasadhikary Thank you so much dada, love your videos

[@CodeInDraw]

One doubt, where i can store token in client (next js) and what is the bestest way to send token from server (node js) like i was looking like if my token is also not exposed to users it will be helpful for me to do things and protect my authenticated data from user so that if a user is developer also cannot misuse the token. Anyways like i wanna know your preference if you wanna do authentication with webapps with next and node ao which method u will choose and why ?

[@ayush_code9849]

I store token in httpOnly cookies and use server actions to call the external apis and there I can access my token.

[@tapasadhikary]

@CodeInDraw first of all, thanks for joining as a member.. I appreciate it! This is an excellent question. There are plenty of ways we handle tokens on the client side. To be honest, there is no solution that is completely secured at the client side. Let me explain: You can store the tokens in the following places at the client side: - Local Storage - Session Storage - IndexedDB - Cookies - In Memory The kind of web security attacks that your application may encounter are: - XSS - CSRF - Stealing Token With Local Storage, Session Storage, and IndexedDB: you need to guard against XSS and Token Stealing With Cookies, you can safeguard from XSS by making the cookies as httpOnly, can excrypt the token to safeguard from the stealing token. Also, if you use sameSite cookie, the CSRF also can be mitigated. Hence, cookies seem to be still a better solution to me considering: - You do not have any cookie length issue - Your cookies are httpOnly - You have sameSite cookie - You have additional layers of XSS prevention at the application level. Long answer.. but that's my take. I hope it was helpful.

[@CodeInDraw]

@@tapasadhikary That's really helpful brother. Thank you so much. I really love to support the creator like you brother 💟. I request please keep going and i will definitely be there to support you and your content. Thankyou ao much ❤️

[@tapasadhikary]

@@CodeInDraw Thanks a lot...I will contrinue giving my best!

[@metakulnft]

Video on service worker PWA

[@ArunKumar-ft5nd]

Hi Tapas how can I join in reactplay meet ups

[@tapasadhikary]

You can just RSVP and come over.. Also CFP details are here if you are interested in speaking on any web dev topics Join me at ReactPlay Bangalore Meetup - August 3, 2024 meetu.ps/e/Nk3Dn/pxlX2/i

[@imkir4n]

Good video brother.

[@tapasadhikary]

Thanks a lot.

[@शुभमकुंवर-न4त]

Video on sevice worker PWA

[@metakulnft]

Video on service worker PWA

[@शुभमकुंवर-न4त]

Video on service worker PWA

[@शुभमकुंवर-न4त]

Video on service worker PWA