javascript-obfuscator 5.4.7 → 5.5.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,13 @@
1
1
  Change Log
2
2
 
3
+ v5.5.1
4
+ ---
5
+ * Fixed leading whitespace of the source code being stripped without being reflected in the source map, shifting all `sourcesContent` and original position mappings. Fixes https://github.com/javascript-obfuscator/javascript-obfuscator/issues/1437
6
+
7
+ v5.5.0
8
+ ---
9
+ * Pro API: reworked large file uploads — fixed `413 Content Too Large` for ~4.4–4.6MB request bodies, and Blob uploads now send the raw source (`blobFormat: 'raw'`) instead of the JSON request body, so uploads always fit the plan's file size cap
10
+
3
11
  v5.4.7
4
12
  ---
5
13
  * Fixed directory obfuscation with a set `sourceMapFileName` making all files share and overwrite one `.map`. Fixes https://github.com/javascript-obfuscator/javascript-obfuscator/issues/817
package/CLAUDE.md CHANGED
@@ -475,15 +475,23 @@ The project includes a browser build at `dist/index.browser.js` that can be used
475
475
  ```bash
476
476
  # Production build
477
477
  npm run build
478
+ # or
479
+ yarn run build
478
480
 
479
481
  # Development watch mode
480
482
  npm run watch
483
+ # or
484
+ yarn run watch
481
485
 
482
486
  # Build TypeScript typings
483
487
  npm run build:typings
488
+ # or
489
+ yarn run build:typings
484
490
 
485
491
  # Linting
486
492
  npm run eslint
493
+ # or
494
+ yarn run eslint
487
495
  ```
488
496
 
489
497
  ## Testing
@@ -1184,24 +1192,32 @@ The project uses **Husky** for git hooks:
1184
1192
  1. **Use watch mode during development**:
1185
1193
  ```bash
1186
1194
  npm run watch
1195
+ # or
1196
+ yarn run watch
1187
1197
  ```
1188
1198
  This rebuilds automatically when you save files.
1189
1199
 
1190
1200
  2. **Run specific tests during development**:
1191
1201
  ```bash
1192
1202
  npm run test:dev
1203
+ # or
1204
+ yarn run test:dev
1193
1205
  ```
1194
1206
  Faster than full test suite.
1195
1207
 
1196
1208
  3. **Check linting before committing**:
1197
1209
  ```bash
1198
1210
  npm run eslint
1211
+ # or
1212
+ yarn run eslint
1199
1213
  ```
1200
1214
  Fix issues before the pre-commit hook runs.
1201
1215
 
1202
1216
  4. **Test memory usage**:
1203
1217
  ```bash
1204
1218
  npm run test:mocha-memory-performance
1219
+ # or
1220
+ yarn run test:mocha-memory-performance
1205
1221
  ```
1206
1222
  Ensure your changes don't cause memory issues.
1207
1223
 
@@ -1209,6 +1225,9 @@ The project uses **Husky** for git hooks:
1209
1225
  ```bash
1210
1226
  npm run test:mocha-coverage
1211
1227
  npm run test:mocha-coverage:report
1228
+ # or
1229
+ yarn run test:mocha-coverage
1230
+ yarn run test:mocha-coverage:report
1212
1231
  ```
1213
1232
  Check test coverage in the generated `coverage/` directory.
1214
1233
 
package/README.md CHANGED
@@ -10,30 +10,10 @@
10
10
 
11
11
  ---
12
12
 
13
- ### Do you use JavaScript Obfuscator at your company?
14
-
15
- 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.
16
-
17
- 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.
18
-
19
- Helpful evidence may include a brief confirmation or, ideally, a 1–2 page reference letter describing:
20
-
21
- - how your team or company used JavaScript Obfuscator;
22
- - why you chose it;
23
- - what problem it helped solve;
24
- - whether it was used in production or an important internal workflow;
25
- - your role and how you are familiar with the usage.
26
-
27
- I can provide a simple draft/template to make this easy.
28
-
29
- Please contact me at: **referenceletter@obfuscator.io**
30
-
31
- Thank you for supporting the project.
32
-
33
- ---
34
-
35
13
  ### :rocket: Obfuscator.io with VM Obfuscation
36
14
 
15
+ [![Obfuscator.io - JavaScript VM Obfuscation](https://raw.githubusercontent.com/javascript-obfuscator/javascript-obfuscator/master/images/obfuscator_io_promo.png)](https://obfuscator.io)
16
+
37
17
  **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.
38
18
 
39
19
  | Protection goal | Free (this package) | [obfuscator.io](https://obfuscator.io) |
@@ -54,6 +34,28 @@ This package provides access to Obfuscator.io API via CLI and Node.js API.
54
34
 
55
35
  ---
56
36
 
37
+ ### Do you use JavaScript Obfuscator at your company?
38
+
39
+ 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.
40
+
41
+ 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.
42
+
43
+ Helpful evidence may include a brief confirmation or, ideally, a 1–2 page reference letter describing:
44
+
45
+ - how your team or company used JavaScript Obfuscator;
46
+ - why you chose it;
47
+ - what problem it helped solve;
48
+ - whether it was used in production or an important internal workflow;
49
+ - your role and how you are familiar with the usage.
50
+
51
+ I can provide a simple draft/template to make this easy.
52
+
53
+ Please contact me at: **referenceletter@obfuscator.io**
54
+
55
+ Thank you for supporting the project.
56
+
57
+ ---
58
+
57
59
  JavaScript Obfuscator is a powerful free obfuscator for JavaScript, containing a variety of features which provide protection for your source code.
58
60
 
59
61
  **Key features:**
@@ -73,6 +75,7 @@ The example of obfuscated code: [github.com](https://github.com/javascript-obfus
73
75
  #### Plugins:
74
76
  * Webpack plugin: [webpack-obfuscator](https://github.com/javascript-obfuscator/webpack-obfuscator)
75
77
  * Webpack loader: [obfuscator-loader](https://github.com/javascript-obfuscator/obfuscator-loader)
78
+ * Esbuild plugin: [esbuild-javascript-obfuscator](https://www.npmjs.com/package/esbuild-javascript-obfuscator)
76
79
  * Gulp: [gulp-javascript-obfuscator](https://github.com/javascript-obfuscator/gulp-javascript-obfuscator)
77
80
  * Grunt: [grunt-contrib-obfuscator](https://github.com/javascript-obfuscator/grunt-contrib-obfuscator)
78
81
  * Rollup: [rollup-plugin-javascript-obfuscator](https://github.com/javascript-obfuscator/rollup-plugin-javascript-obfuscator)