Reason as mentioned in the #10 we will use the JWT based auth but since the request comes from the client side browser the token will get reflected in the browser's tab thus in order to block it we need to fetch data on the server side so server side rendering in the NextJS can keep async fetch function in the server thus the JWT token does not get exposed.
Reason as mentioned in the #10 we will use the JWT based auth but since the request comes from the client side browser the token will get reflected in the browser's tab thus in order to block it we need to fetch data on the server side so server side rendering in the NextJS can keep async fetch function in the server thus the JWT token does not get exposed.