Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork1.7k
Obfuscation performance#1206
-
We know the fact that most of the time the code itself start to works a bit slower after obfuscation. This is okay sometimes, when the obfuscated code is not very important part of the app that do some important calculations and actually can affect user experience. {compact:true,simplify:true,identifierNamesGenerator:'mangled-shuffled',renameGlobals:true,splitStrings:true,splitStringsChunkLength:3,stringArray:true,stringArrayEncoding:['rc4'],stringArrayShuffle:true,transformObjectKeys:true,unicodeEscapeSequence:true,seed:0} it takes from 50 to 100 ms to obfuscate the source! So my question is can we improve the obfuscation speed? |
BetaWas this translation helpful?Give feedback.
All reactions
Replies: 1 comment 2 replies
-
You should obfuscate in your build process, so it doesn't affect the loading times. |
BetaWas this translation helpful?Give feedback.
All reactions
-
The thing is that I have very specific case where I need to reobfuscate code each request. |
BetaWas this translation helpful?Give feedback.
All reactions
-
Got it. Then I'm not sure how to deal with it, as the obfuscator is blazing fast for its purpose. Maybe try running it on Bun, compiling it to wasm? |
BetaWas this translation helpful?Give feedback.