0.13.0 plans
See original GitHub issueMain internal feature - block scope analyzer that will prepare block scope data for using in transformers.
Other features:
- internal
mangling
of variable names instead of usingesmangle
- object keys obfuscation https://github.com/javascript-obfuscator/javascript-obfuscator/issues/81#issuecomment-332156650
- ???
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Eclipse Requirements Modeling Framework™ 0.13.0
This release targets a defined set of other Eclipse components (e.g. platform, EMF, etc.) originating from the following release trains:.
Read more >Release plan of 0.13.0 - Google Groups
For now the latest 0.13.0-beta7 is based on the latest Chromium stable 48. As we are approaching the final release, and Chromium 49...
Read more >ExpertSDR3 0.13.0 status update - Эксперт Электроникс
The plan is to release the ExpertSDR3 0.13.0 in 5 weeks. Before we publish this version, it will go through a thorough testing...
Read more >Nikon Microscope Objective Lens NIKON CF Plan 5X ... - eBay
Find many great new & used options and get the best deals for Nikon Microscope Objective Lens NIKON CF Plan 5X/0.13 ∞/0 with...
Read more >MINECRAFT PE 0.13.0 | DUPLICATION GLITCH - Pinterest
MINECRAFT PE 0.13.0 | DUPLICATION GLITCH. Video by ... Minecraft House Plans, Minecraft Modern, Minecraft House Tutorials, Minecraft Decorations ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @slig. Thank you for your input. I managed to split the bundle in chunks and obfuscate only one of them. I think I can live with that.
My initial thought was to obfuscate only parts (ex. one module or even one line) of one bundle, though. That would leave webpack bootstrap and other non-secret modules intact.
With my initial idea I could:
// javascript-obfuscator:enable
and// javascript-obfuscator:disable
,// javascript-obfuscator:enable
on the beginningand everything else would remain as is.
I’ll think about this. Like new option that will disable obfuscation by default.
Looking for option name.