javascript-obfuscator 5.4.2 → 5.4.4

package/CHANGELOG.md

@@ -1,5 +1,16 @@
 Change Log
 
+v5.4.4
+---
+* Optimized scope identifiers transformer performance
+* Optimized identifier renaming performance by reusing scope analysis between transformers
+* Fixed `Invalid regular expression` error when obfuscating code that uses ES2025 RegExp pattern modifiers (e.g. `/(?i:abc)/`). Fixes https://github.com/javascript-obfuscator/javascript-obfuscator/issues/1410
+* Fixed `SyntaxError` when obfuscating a class that extends a boolean literal (e.g. `class C extends true {}`). Fixes https://github.com/javascript-obfuscator/javascript-obfuscator/issues/1131
+
+v5.4.3
+---
+* Fixed `controlFlowFlattening` occasionally dropping the `?.` short-circuit on `foo?.(arg)` calls, causing `TypeError: <X> is not a function`. Fixes https://github.com/javascript-obfuscator/javascript-obfuscator/issues/1408
+
 v5.4.2
 ---
 * Fixed obfuscated code hanging in Bun when `selfDefending` is enabled. Fixes https://github.com/javascript-obfuscator/javascript-obfuscator/issues/1404

package/CLAUDE.md

@@ -42,7 +42,7 @@
 - **Parser**: Acorn 8.8.2 (ES3-ES2020 support)
 - **Code Generator**: @javascript-obfuscator/escodegen 2.3.0
 - **AST Traversal**: @javascript-obfuscator/estraverse 5.4.0
-- **DI Framework**: InversifyJS 6.0.1
+- **DI Framework**: InversifyJS 7.10.8
 - **Testing**: Mocha 10.4.0 + Chai 4.3.7
 - **Build System**: Webpack 5.75.0
 
@@ -210,7 +210,7 @@ The obfuscation process follows a multi-stage pipeline defined in `JavaScriptObf
 
 ### Dependency Injection Architecture
 
-The project uses **InversifyJS** for dependency injection, providing:
+The project uses **InversifyJS v7** for dependency injection, providing:
 
 - **Modularity**: Clean separation of concerns
 - **Testability**: Easy mocking and testing
@@ -219,6 +219,13 @@ The project uses **InversifyJS** for dependency injection, providing:
 
 All components are registered in container modules located in `src/container/modules/`.
 
+**Key Changes in InversifyJS v7:**
+- Container modules now use `ContainerModuleLoadOptions` instead of separate `bind`, `unbind`, etc. parameters
+- `getNamed`, `getTagged`, etc. are replaced by `get(serviceId, { name: ... })` or `get(serviceId, { tag: ... })`
+- `load()` and `unload()` are now async, with `loadSync()` and `unloadSync()` alternatives for synchronous operations
+- Types like `Context`, `Newable`, `Factory` are now directly exported instead of through `interfaces` namespace
+- Custom metadata and middleware features have been removed
+
 ## Key Components Deep Dive
 
 ### 1. JavaScriptObfuscator (Main Engine)

package/README.md

@@ -4,17 +4,34 @@
   Author: Timofei Kachalov
   -->
 
-#### You can support this project by donating:
-* (Github) https://github.com/sponsors/sanex3339
-
-Huge thanks to all supporters!
-
 # JavaScript obfuscator
 
 ![logo](https://raw.githubusercontent.com/javascript-obfuscator/javascript-obfuscator/master/images/logo.png)
 
 ---
 
+### Do you use JavaScript Obfuscator at your company?
+
+JavaScript Obfuscator has reached over **1 million npm downloads per week**. I am currently preparing an **EB-1 immigration case** and collecting independent evidence of the project’s real-world professional usage and impact.
+
+If you use JavaScript Obfuscator in a company project — especially at a well-known company, large organization, or widely used product — I would be very grateful if you could contact me.
+
+Helpful evidence may include a brief confirmation or, ideally, a 1–2 page reference letter describing:
+
+- how your team or company used JavaScript Obfuscator;
+- why you chose it;
+- what problem it helped solve;
+- whether it was used in production or an important internal workflow;
+- your role and how you are familiar with the usage.
+
+I can provide a simple draft/template to make this easy.
+
+Please contact me at: **referenceletter@obfuscator.io**
+
+Thank you for supporting the project.
+
+---
+
 ### :rocket: Obfuscator.io with VM Obfuscation
 
 **Obfuscator.io** adds **VM-based bytecode obfuscation** to this package - your JavaScript functions are compiled to custom bytecode that runs on an embedded virtual machine. Each build produces unique opcodes and VM structure, making reverse engineering and automated deobfuscation dramatically harder.