Eval(Binary) expression in new javaScript Engine

[#1]

Hello friends,

In the past I encrypted my expression in After Effects (using jsxbin) and inserted the binary code into eval () and everything worked fine.
And now with the new javaScript expression engine in After Effects it doesn't work and brings up an error message: SyntaxError: Invalid or Unexpected Token.
How can this be corrected in the new expression engine?

example: 

eval("@JSXBIN@ES@2.0@MyBbyBn0ABbAn0ABJAnASzBjBByBndFffABB40BiAABAzACByB")

eval("@JSXBIN@ES@2.0@MyBbyBn0ABbAn0ABJAnASzBjBByBndFffABB40BiAABAzACByB");

[#2]

Hello friends,

In the past I encrypted my expression in After Effects (using jsxbin) and inserted the binary code into eval () and everything worked fine.
And now with the new javaScript expression engine in After Effects it doesn't work and brings up an error message: SyntaxError: Invalid or Unexpected Token.
How can this be corrected in the new expression engine?

example: 

eval("@JSXBIN@ES@2.0@MyBbyBn0ABbAn0ABJAnASzBjBByBndFffABB40BiAABAzACByB")

eval("@JSXBIN@ES@2.0@MyBbyBn0ABbAn0ABJAnASzBjBByBndFffABB40BiAABAzACByB");

[#3]

The new engine is JavaScript, not ExtendScript, so JSXBIN only works in the legacy engine from now on. If you want to look into hiding your sourcecode, look into JavaScript obfuscation techniques, but watch out for a performance hit.

[#4]

yes, what Justin says. Simple minification might be the best balance - it does not create any performance problems and makes your expressions somewhat hard to read. There is simply no reliable way to protect your expressions - it is just about making it less convenient to hack them.

[#5]

Thanks