terser 4.3.5 → 4.3.9

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # Changelog
 
+## v4.3.9
+ - Fixed issue with mangle's `keep_fnames` option, introduced when adding code to keep variable names of anonymous functions
+
+## v4.3.8
+
+ - Typescript typings fix
+
+## v4.3.7
+
+ - Parsing of regex options in the CLI (which broke in v4.3.5) was fixed.
+ - typescript definition updates
+
+## v4.3.6
+
+(crash hotfix)
+
 ## v4.3.5
 
  - Fixed an issue with DOS line endings strings separated by `\` and a new line.

package/README.md

@@ -261,7 +261,7 @@ way to use this is to use the `regex` option like so:
 terser example.js -c -m --mangle-props regex=/_$/
 ```
 
-This will mangle all properties that start with an
+This will mangle all properties that end with an
 underscore. So you can use it to mangle internal methods.
 
 By default, it will mangle all properties in the
@@ -289,32 +289,32 @@ console.log(x.calc());
 ```
 Mangle all properties (except for JavaScript `builtins`) (**very** unsafe):
 ```bash
-$ terser example.js -c -m --mangle-props
+$ terser example.js -c passes=2 -m --mangle-props
 ```
 ```javascript
-var x={o:0,_:1,l:function(){return this._+this.o}};x.t=2,x.o=3,console.log(x.l());
+var x={o:3,t:1,i:function(){return this.t+this.o},s:2};console.log(x.i());
 ```
 Mangle all properties except for `reserved` properties (still very unsafe):
 ```bash
-$ terser example.js -c -m --mangle-props reserved=[foo_,bar_]
+$ terser example.js -c passes=2 -m --mangle-props reserved=[foo_,bar_]
 ```
 ```javascript
-var x={o:0,foo_:1,_:function(){return this.foo_+this.o}};x.bar_=2,x.o=3,console.log(x._());
+var x={o:3,foo_:1,t:function(){return this.foo_+this.o},bar_:2};console.log(x.t());
 ```
 Mangle all properties matching a `regex` (not as unsafe but still unsafe):
 ```bash
-$ terser example.js -c -m --mangle-props regex=/_$/
+$ terser example.js -c passes=2 -m --mangle-props regex=/_$/
 ```
 ```javascript
-var x={o:0,_:1,calc:function(){return this._+this.o}};x.l=2,x.o=3,console.log(x.calc());
+var x={o:3,t:1,calc:function(){return this.t+this.o},i:2};console.log(x.calc());
 ```
 
 Combining mangle properties options:
 ```bash
-$ terser example.js -c -m --mangle-props regex=/_$/,reserved=[bar_]
+$ terser example.js -c passes=2 -m --mangle-props regex=/_$/,reserved=[bar_]
 ```
 ```javascript
-var x={o:0,_:1,calc:function(){return this._+this.o}};x.bar_=2,x.o=3,console.log(x.calc());
+var x={o:3,t:1,calc:function(){return this.t+this.o},bar_:2};console.log(x.calc());
 ```
 
 In order for this to be of any use, we avoid mangling standard JS names by
@@ -820,7 +820,7 @@ If you happen to need the source map as a raw object, set `sourceMap.asObject` t
   case a value of `20` or less is recommended.
 
 - `side_effects` (default: `true`) -- Pass `false` to disable potentially dropping
-  functions marked as "pure".  A function call is marked as "pure" if a comment
+  function calls marked as "pure".  A function call is marked as "pure" if a comment
   annotation `/*@__PURE__*/` or `/*#__PURE__*/` immediately precedes the call. For
   example: `/*@__PURE__*/foo();`
 

package/bin/terser

@@ -368,6 +368,9 @@ function parse_js(flag) {
                         options[name] = value;
                     } else if (value instanceof Terser.AST_Array) {
                         options[name] = value.elements.map(to_string);
+                    } else if (value instanceof Terser.AST_RegExp) {
+                        value = value.value;
+                        options[name] = new RegExp(value.source, value.flags);
                     } else {
                         options[name] = to_string(value);
                     }