No matter how hard you try to obfuscate JS, it's easy to de-obfuscate it. There are many plugins available for this purpose. For example, there is Javascript Deobfuscator for Firefox.
Do minify though.
It will save you and your users some bandwidth, improve load times and everybody's happy.
YUI Compressor is generally considered the best option for minifying JavaScript. But don't imagine anything will protect your code if anyone wants to steal it — that's a fool's errand and no professional will waste his time that way.
Also, remember that if an attacker is determined enough, they will be able to put together the original code, obfuscating just deters casual attackers and just makes it harder for the more experienced ones.
Obfuscators can be beautified quite easily. This TypeScript project is not a silver bullet by any means, but does make beautifying MUCH more difficult depending on the parameters used.
Strings are converted into hexadecimal and you will never be able to get your original code back so keep a safe copy.
Also, you can run a minifier before using this but do not run this and then use a minifier. Things will likely break.
Here is an online playground to get your feet wet.
If you don't want to use webpack, gulp, grunt - the online playground is also available for you to run locally credit to Tiago Serafim.
Javascript needs to be interpreted by the browser, and hence has to be readable by the browser... and thus cannot be obfuscated. The ones you find on google are as good as it gets. They can make the javascript slightly hard to read by hand, but on the other hand it's pretty easy to de-obfuscate them.
There is one option if you want to do something to protect your code. You can move your code to the serverside using a server side javascript solution, such as node.js. This will probably make your app overall more complicated but might be worth it if you are really serious about protecting your code.
The meaning of obfuscating is: changing the code in a matter that the code will be less readable, but EXACT same functionality and logic!
A very good free obfuscator that I'm using usually, because it is: 1] free :) 2] one way obfuscating! some tools change your functions, by 'eval', which can easily show your ORGINAL code. 3] add random code inside for harder tracking. 4] and also, cleans line-breaks + empty spaces.
I found an awesome obfuscator tool at here: http://javascript-obfuscator.org. The tool give me bunch of options which I can choose to protect my js source code. However, some of them would make a trade-off between code protection and code size / speed.
发布评论
评论（10）
缩小“压缩”代码。
打包“压缩”和“混淆”代码。
我认为最受欢迎的打包程序是：
http://dean.edwards.name/packer/
不过 Google Closure 是评价最高的压缩器之一还可以使用附加选项进行打包：
http://code.google.com/closure/compiler/docs /api-tutorial3.html#enable
Minification "compresses" code.
Packing "compresses" and "obfuscates" code.
The most popular packer I believe to be:
http://dean.edwards.name/packer/
However Google Closure one of the highest rated minifiers can also do packing with additional options:
http://code.google.com/closure/compiler/docs/api-tutorial3.html#enable
混淆：不要这样做。
无论你多么努力地试图混淆 JS，去混淆它都很容易。有许多插件可用于此目的。例如，Firefox 有 Javascript Deobfuscator。
不过要缩小。
它将为您和您的用户节省一些带宽，缩短加载时间，让每个人都满意。
Google Closure 编译器
MinifyJS
YUI 压缩器
还有更多...
Obfuscation: Don't do it.
No matter how hard you try to obfuscate JS, it's easy to de-obfuscate it. There are many plugins available for this purpose. For example, there is Javascript Deobfuscator for Firefox.
Do minify though.
It will save you and your users some bandwidth, improve load times and everybody's happy.
Google Closure Compiler
MinifyJS
YUI Compressor
many more...
YUI Compressor 通常被认为是缩小 JavaScript 的最佳选择。但是，如果有人想窃取您的代码，请不要想象任何东西都会保护您的代码 - 这是愚蠢的差事，没有专业人士会这样浪费时间。
YUI Compressor is generally considered the best option for minifying JavaScript. But don't imagine anything will protect your code if anyone wants to steal it — that's a fool's errand and no professional will waste his time that way.
我想推荐另一个工具来缩小/压缩/混淆javascript： http://jscrambler.com
目前它是网络但即将推出允许远程调用的 API。
我在这里找到了已知的 javascript 混淆器列表： http://www .malwareguru.org/mediawiki/index.php/Collection_of_tools_for_javascript_obfuscation_%28javascript_packers%29
I would like to suggest another tool to minify / compress /obfuscate javascript: http://jscrambler.com
Currently it is web only but an API is coming that will allow for remote call.
I have found a list of known javascript obfucators here: http://www.malwareguru.org/mediawiki/index.php/Collection_of_tools_for_javascript_obfuscation_%28javascript_packers%29
Obfuscriptor 是另一个免费的 Javascript 混淆器。
编辑：死链接，现在是 NSFW 网站 (http://www.obfuscriptor. com/)
上次 Archive.org 保存： https://web.archive.org/web/20140202025012/http://www.obfuscriptor.com/
混淆后的代码看起来确实像垃圾。类似于 f/$873h3#"!=]f。
对于非常小的文件，它提供了我所见过的最佳压缩率。
Obfuscriptor is another free Javascript obfuscator.
EDIT: Dead link, this is now a NSFW website (http://www.obfuscriptor.com/)
Last Archive.org save: https://web.archive.org/web/20140202025012/http://www.obfuscriptor.com/
The obfuscated code really looks like garbage. Something like f/$873h3#"!=]f.
And for non trivially small files it provides the best compression rates I've seen.
这是一个简单的基于网络的：
http://www.javascriptobfuscator.com/default.aspx
另外，请记住，如果攻击者有足够的决心，他们将能够将原始代码放在一起，混淆只会阻止临时攻击者，并且只会让更有经验的攻击者变得更加困难。
Here's an easy web based one:
http://www.javascriptobfuscator.com/default.aspx
Also, remember that if an attacker is determined enough, they will be able to put together the original code, obfuscating just deters casual attackers and just makes it harder for the more experienced ones.
混淆器可以很容易地美化。 这个 TypeScript 项目无论如何都不是灵丹妙药，但确实可以美化更多困难取决于所使用的参数。
字符串被转换为十六进制，您将永远无法取回原始代码，因此请保留安全副本。
另外，您可以在使用它之前运行一个压缩器，但不要运行它然后再使用压缩器。事情可能会破裂。
这里是一个让您涉足的在线游乐场。
如果您不想使用 webpack、gulp、grunt - 也可以使用在线游乐场 供您在本地向 Tiago Serafim 提供信用。
JavaScript 混淆器工具 - 图片来源 - Timofey Kachalov
Obfuscators can be beautified quite easily. This TypeScript project is not a silver bullet by any means, but does make beautifying MUCH more difficult depending on the parameters used.
Strings are converted into hexadecimal and you will never be able to get your original code back so keep a safe copy.
Also, you can run a minifier before using this but do not run this and then use a minifier. Things will likely break.
Here is an online playground to get your feet wet.
If you don't want to use webpack, gulp, grunt - the online playground is also available for you to run locally credit to Tiago Serafim.
JavaScript Obfuscator Tool - Credit - Timofey Kachalov
嘿，没有这样的事情。
JavaScript 需要被浏览器解释，因此必须能够被浏览器读取……因此不能被混淆。你在谷歌上找到的那些都是最好的。它们可能会使 javascript 用手阅读有点困难，但另一方面，去混淆它们却很容易。
如果您想采取一些措施来保护您的代码，有一种选择。您可以使用服务器端 JavaScript 解决方案（例如 Node.js）将代码移至服务器端。这可能会使您的应用程序整体更加复杂，但如果您真的认真保护您的代码，那么可能是值得的。
Hey there is no such thing.
Javascript needs to be interpreted by the browser, and hence has to be readable by the browser... and thus cannot be obfuscated. The ones you find on google are as good as it gets. They can make the javascript slightly hard to read by hand, but on the other hand it's pretty easy to de-obfuscate them.
There is one option if you want to do something to protect your code. You can move your code to the serverside using a server side javascript solution, such as node.js. This will probably make your app overall more complicated but might be worth it if you are really serious about protecting your code.
混淆的含义是：更改代码会降低代码的可读性，但功能和逻辑完全相同！
我经常使用的一个非常好的免费混淆器，因为它是：
1]免费:)
2] 单向混淆！一些工具通过“eval”更改您的功能，这可以轻松显示您的原始代码。
3]在内部添加随机代码以实现更难的跟踪。
4]并且还清除换行符+空格。
完整网址：http://freejsobfuscator.com/
The meaning of
obfuscatingis:changing the code in a matter that the code will be less readable, but EXACT same functionality and logic!
A very good free obfuscator that I'm using usually, because it is:
1] free :)
2] one way obfuscating! some tools change your functions, by 'eval', which can easily show your ORGINAL code.
3] add random code inside for harder tracking.
4] and also, cleans line-breaks + empty spaces.
Full URL: http://freejsobfuscator.com/
我在这里找到了一个很棒的混淆器工具：http://javascript-obfuscator.org。
该工具为我提供了很多选项，我可以选择它们来保护我的 js 源代码。然而，他们中的一些人会在代码保护和代码大小/速度之间进行权衡。
I found an awesome obfuscator tool at here: http://javascript-obfuscator.org.
The tool give me bunch of options which I can choose to protect my js source code. However, some of them would make a trade-off between code protection and code size / speed.