Conditional Comments
You can selectively disable obfuscation for specific parts of your code using special comments.
Useful when you need to keep specific configuration blocks or version strings readable in the output - without giving up obfuscation for the rest of the file.
The obfuscator reads these comments from its input, so keep them through any build step that runs before obfuscation; a minifier that strips comments first removes them.
What "disable" actually skips
A disabled region only skips direct transformations of the nodes inside it - obfuscating a declaration at the point it is declared. Child transformations still apply, so a reference inside a disabled block to an identifier that was renamed at its declaration elsewhere is still renamed:
If you need a name to stay readable everywhere it appears, disabling one block is not enough; keep its declaration out of an obfuscated region too, or use reservedNames.
Under vmObfuscation, disable only works on whole functions. A function inside a disabled region is not virtualized. A disabled region nested inside a function that gets virtualized is still compiled into bytecode along with the rest of that function's body - the readable form does not survive. Only code that is disabled at the root level (outside any virtualized function) stays plain in the output.