Honestly, you don’t want production to tell users what your exact errors are, and especially not what the source code looks like and where to find the problem exactly.
Production errors should mostly go “Well, this was on (y)our side, sorry about that” and nothing more.
If it’s in the minified front end code it’s already client side, of course you don’t show it to the user but they could find out if they wanted to. Server side errors are where you really have to watch out not to give out any details, but then logging them is also easier since it’s already on the server.
Honestly, you don’t want production to tell users what your exact errors are, and especially not what the source code looks like and where to find the problem exactly.
Production errors should mostly go “Well, this was on (y)our side, sorry about that” and nothing more.
If it’s in the minified front end code it’s already client side, of course you don’t show it to the user but they could find out if they wanted to. Server side errors are where you really have to watch out not to give out any details, but then logging them is also easier since it’s already on the server.
Ah you’re right, I’m thinking too much like a backend dev!
No, not all error have security implications
deleted by creator
Yeah, if one really wants obfuscation for JS, then it requires an extra build step. E.g. this: JavaScript-obfuscator