You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Strings inside template literals are currently not obfuscated.
For example:
console.log(`Hello World`)
Will preserve the Hello world 1:1 into the generated code without obfuscation.
Describe the solution you'd like
Note
Codeblocks below are using ´ so they are displayed correctly.
Template strings should be obfuscated, there are multiple ways to achieve this:
replace with normal string concats (eg ´Hello ${name}´ gets turned into "Hello " + name – where "Hello " is processed like a normal string with string concealing etc)
replace with string literals (eg ´Hello world´ into ´${"Hello world"}´)
Tagged function calls can be turned into regular function calls instead:
test´hello ${world}´ -> test(["hello "], world)
The text was updated successfully, but these errors were encountered:
Yes I plan to use Babel in the future, maybe for a 2.0 rewrite? I noticed Babel tools are very fast and has nice APIs that Webcrack and other projects use (ex: referenced identifiers)
Is your feature request related to a problem? Please describe.
Strings inside template literals are currently not obfuscated.
For example:
Will preserve the
Hello world
1:1 into the generated code without obfuscation.Describe the solution you'd like
Note
Codeblocks below are using ´ so they are displayed correctly.
Template strings should be obfuscated, there are multiple ways to achieve this:
´Hello ${name}´
gets turned into"Hello " + name
– where "Hello " is processed like a normal string with string concealing etc)´Hello world´
into´${"Hello world"}´
)Tagged function calls can be turned into regular function calls instead:
test´hello ${world}´
->test(["hello "], world)
The text was updated successfully, but these errors were encountered: