Hey, Mirko! thanks for asking the question. Sometimes you need to console your environment variable values to check why it's undefined or not working, this may cause your credentials at risk.
Online since 1990 Yes! I started with Gopher. I do modern Web Component Development with technologies supported by **all** WHATWG partners (Apple, Google, Microsoft & Mozilla)
Online since 1990 Yes! I started with Gopher. I do modern Web Component Development with technologies supported by **all** WHATWG partners (Apple, Google, Microsoft & Mozilla)
console.log can log everything the user can access in the Inspector.
console.log can only print unwanted credentials when the back-end provided them, there for you imply everything coming from the back-end is a security risk.
Or saying console.log is a security risk is just stupid.
Hi! Why console.logs are a security risk?
Hey, Mirko! thanks for asking the question. Sometimes you need to console your environment variable values to check why it's undefined or not working, this may cause your credentials at risk.
Great, now we can label all SSR code as a 'security risk'
Hey, I didn't mean that
But you said so.
console.log
can log everything the user can access in the Inspector.console.log
can only print unwanted credentials when the back-end provided them, there for you imply everything coming from the back-end is a security risk.Or saying console.log is a security risk is just stupid.
I strongly disagree. I didn't mean that at all. Here I just mentioned a situation ,how a user can put his/her credentials on risk.
Interesting 😊 thats the only thing that always worked for me 😂
😂
Maybe for performance reasons? Like it runs on the main thread in the browser...
Performance may be a reason 🙄