-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Obfuscation by using UglifyJS2 #150
Comments
What do you mean? I believe the goal of Closure Compiler is to minify, just like for UglifyJS. |
Thanks for the reply. Yes I mean this. Ok but does uglifyjs support mangle of "private" variables that starts with underscore? There is pull request in uglifyjs #309 |
You should probably separate "variables" and "properties". You're talking about "private" properties. As you can see from a the this comment on the pull request, a lot of assumptions have to be made about the code, probably breaking a lot of code. For code that's a bit more complex, "advanced" requires lots of annotations, and often compiling code twice breaks it. E.g. the jQuery project decided that it wasn't worth trying to conform to how that works. If you need smaller code, consider refactoring by using "project-global" variables and functions. |
+1 any updates? |
UglifyJS does minification, not obfuscation. As the main concern is about shorter property keys, I'm closing this in favor of #81. |
Maybe this can help to someone's that the bosses says: "Should be obfuscated". https://www.npmjs.com/package/obfuscator |
I know that UglifyJS is good for minimization but I need to Obfuscate fully like Closure Compiler do. Is it possible with UglifyJS?
The text was updated successfully, but these errors were encountered: