Common but not consistent.  The main purpose is to be able to leave comments in the JavaScript, and then these comments can be removed during obfuscation. Another reason is some global javascript should't be static, so to avoid any conflicts I'm using ObfuscateJs as well.

To be honest, I'm not too worries about it here because there needs to be a HttpServer-based mixin specifically made for browser exploitation. Because it's kind of a hassle for manage obfuscation on a module's level. Ideally that mixin should set "OBFUSCATE" to true by default, and then you can manually turn it off as one of the DefaultOptions. The actual implemented is still open for discussion as a redmine ticket.