React.js is one of the most popular JavaScript libraries. The 2018 "State of JavaScript" survey puts React as the front-end framework of choice, wi...
For further actions, you may consider blocking this person and/or reporting abuse
Note that this doesn't make the code secret, or impossible to reverse-engineer, it only makes these things harder.
What is also does is:
This last point is particularly scary, as if the company feels like it, or if they're bought later on and their new buyer feels like it, they can inject their own analytics code, cryptominer or even malware on your website, and you would never know about it.
You should never rely on the front-end for your security, therefore you should definitely considers the cons before implementing this.
You do raise some pertinent points, so let me clear our stance on those:
First, it's true that this doesn't encrypt your code (you can't encrypt JavaScript). The objective of obfuscation is to greatly increase the cost of reverse-engineering attempts, which is useful when you want to ensure that your proprietary code is not on plain sight nor easily retrievable. While this tutorial focuses on obfuscation, Jscrambler is not an obfuscation tool; it provides a total of 3 JavaScript protection layers (including code locks and self-defending).
As for the other concerns you raised:
We absolutely agree that you shouldn't rely on front-end security alone. But you shouldn't also dismiss it when you have proprietary code which can be stolen or tampered with.