sequence as class property breaks everything

[dilame]

Valid JS code

class Foo {
  [(1, Symbol.asyncIterator)]() {}
}

obfuscated as

class Foo {
    [0x1, Symbol['asyncIterator']]() {
    }
}

invalid js code. The bug exists in the latest 0.x.x and latest 1.x.x versions.

It's very important bug, TypeScript generates such code, i can't even fix it.

[sanex3339]

Problem in escodegen again =(
Will try to create the PR there.

[sanex3339]

The PR estools/escodegen#415

[sanex3339]

The PR here:
#639

[sanex3339]

will release 1.1.1 in an hour.

[sanex3339]

New 1.1.1 version with the fix has been released

[dilame]

Wow, thank you!
Let me use the ability and ask you something - do you plan to support ESNext? I want to use ES private fields and nullish coalescing.
Is there any way to tell the obfuscator to ignore parts it can not parse?

[sanex3339]

Hi. Obfuscator supports only stage4 features that are implemented both in acorn, estraverse, and escodegen.
The last two packages are the bottleneck. Currently, I created the PRs with optional chaining support:
estools/escodegen#412
estools/estraverse#113

But one week has passed since then and still no activity there.

You can go there and let the maintainer know that these PRs are important for you.

So until the support of each feature, the best way is to use babel BEFORE obfuscator to transpile unsupported features.

[sanex3339]

Obfuscator has been updated on 1.1.1 everywhere.
You can test it here: https://obfuscator.io/