However I agree that in the end outside of making it more readable, it's not making a huge difference.
This is front-end code, that gets deliberately sent to the browser. With enough work, someone can deobfuscate such code manually.
I think this title is misleading, it makes it seem like more than just the unobfuscated code has been exposed.
> Remember: Always disable sourcemaps in production!
Or don't. One can have serious doubts that the person who wrote this in the README themselves understands (and can articulate the reasons) why they have this position.
There is a non-zero possibility that this wasn't even an accident.
In any case, GitHub isn't an unredactable, append-only ledger. "Archiving" this on a site that is no less subject to DMCA takedowns than any other site but that differs from other sites in having exceptionally fast turnaround times was not an especially well-informed or thoughtful move.
I wish I could downvote this comment from the README.
Minification to reduce bandwidth is noble. But to obfuscate? Why?
4ggr0•31m ago
I guess the same thing applies here, https://www.reddit.com/r/webdev/comments/1onnzlj/comment/nmy...
> This is not "exposing" their source code. While yes, it may not be minified and it's slightly more human readable, it's not exposing any additional logic. Remember, obfuscation is not security.
[0]https://news.ycombinator.com/item?id=45804664