Ultimately the client code must run on the client so there is no way to make sure that your code stays private.
You can of course obfuscate/minify/uglify it but must not rely on its secrecy (especially from a security perspective)
Similar to my thoughts: anyone with access to the client endpoint necessarily has access to the source. And removing the sourcemap is merely a cosmetic choice with no real source security improvement.
This is also one of the reasons to never trust the client with anything you cannot control on the server side (typically a bearer)
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Ultimately the client code must run on the client so there is no way to make sure that your code stays private.
You can of course obfuscate/minify/uglify it but must not rely on its secrecy (especially from a security perspective)
Similar to my thoughts: anyone with access to the client endpoint necessarily has access to the source. And removing the sourcemap is merely a cosmetic choice with no real source security improvement.
This is also one of the reasons to never trust the client with anything you cannot control on the server side (typically a bearer)