Michael Brasington

I believe this error has to do with escodegen or acorn, not with the obfuscator itself. I don't know how to fix this.

Fixed in 2.0 (Currently [2.0.0-alpha.2](https://www.npmjs.com/package/js-confuser/v/2.0.0-alpha.2)). The 2.0 version nows uses Babel's parser and generator and is more suited for modern JavaScript syntax.

No, PRs would be welcomed to implement it

Great find, will fix this for next release.

I will get to work on this

You are right. The new behavior will just be an infinite loop as the default countermeasure. I will change this for next update.

Hi this is already done with `Control Flow Flattening` ```js // Input while(cond) { /* ... */ } var filler1; var filler2; // Output var C9ao9H = -657; var jp6fQY...

Closing for now

@fuzzbuck The [countermeasures](https://github.com/MichaelXF/js-confuser/blob/master/docs/Countermeasures.md) is configurable by setting it a string, it can be a custom callback. This issue is related to the default behavior (no value provided) is incorrect. I...

Hi, can you provide the entire error stack so I can understand better