You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just noticed that when using runTimeConfig.public, these env variables are exposed on the front-end; wouldn't it be better to only have them exposed server-side to avoid exposing these CDA token publicly?
Added screenshots for clarity:
Thank you!
The text was updated successfully, but these errors were encountered:
Hmm, I tried to make the token private: the server-side page generation is all OK, but the rehydration then fails because on the client side useQuery() cannot find the token. What is the best practice in these cases with Nuxt?
I'm not too sure to be honest - maybe the best practice would be to make useQuery() a server-side composable so that it has access to the relevant API token?
Hi Dato and happy new year!
Just noticed that when using
runTimeConfig.public
, these env variables are exposed on the front-end; wouldn't it be better to only have them exposed server-side to avoid exposing these CDA token publicly?Added screenshots for clarity:
Thank you!
The text was updated successfully, but these errors were encountered: