Add property name mangler
We only touch properties that are present in an object literal, or which are
assigned to. Example:
x = { foo: 1 };
x.bar = 2;
x["baz"] = 3;
x[cond ? "qwe" : "asd"] = 4;
console.log(x.stuff);
The names "foo", "bar", "baz", "qwe" and "asd" will be mangled, and the
resulting mangled names will be used for the same properties throughout the
code. The "stuff" will not be, since it's just referenced but never
assigned to.
This *will* break most of the code out there, but could work on carefully
written code: do not use eval, do not define methods or properties by
walking an array of names, etc. Also, a comprehensive list of exclusions
needs to be passed, to avoid mangling properties that are standard in
JavaScript, DOM, used in external libraries etc.
2015-03-14 09:22:28 +00:00
|
|
|
/***********************************************************************
|
|
|
|
|
|
|
|
|
|
A JavaScript tokenizer / parser / beautifier / compressor.
|
2020-05-05 13:07:33 +00:00
|
|
|
https://github.com/mishoo/UglifyJS
|
Add property name mangler
We only touch properties that are present in an object literal, or which are
assigned to. Example:
x = { foo: 1 };
x.bar = 2;
x["baz"] = 3;
x[cond ? "qwe" : "asd"] = 4;
console.log(x.stuff);
The names "foo", "bar", "baz", "qwe" and "asd" will be mangled, and the
resulting mangled names will be used for the same properties throughout the
code. The "stuff" will not be, since it's just referenced but never
assigned to.
This *will* break most of the code out there, but could work on carefully
written code: do not use eval, do not define methods or properties by
walking an array of names, etc. Also, a comprehensive list of exclusions
needs to be passed, to avoid mangling properties that are standard in
JavaScript, DOM, used in external libraries etc.
2015-03-14 09:22:28 +00:00
|
|
|
|
|
|
|
|
-------------------------------- (C) ---------------------------------
|
|
|
|
|
|
|
|
|
|
Author: Mihai Bazon
|
|
|
|
|
<mihai.bazon@gmail.com>
|
|
|
|
|
http://mihai.bazon.net/blog
|
|
|
|
|
|
|
|
|
|
Distributed under the BSD license:
|
|
|
|
|
|
|
|
|
|
Copyright 2012 (c) Mihai Bazon <mihai.bazon@gmail.com>
|
|
|
|
|
|
|
|
|
|
Redistribution and use in source and binary forms, with or without
|
|
|
|
|
modification, are permitted provided that the following conditions
|
|
|
|
|
are met:
|
|
|
|
|
|
|
|
|
|
* Redistributions of source code must retain the above
|
|
|
|
|
copyright notice, this list of conditions and the following
|
|
|
|
|
disclaimer.
|
|
|
|
|
|
|
|
|
|
* Redistributions in binary form must reproduce the above
|
|
|
|
|
copyright notice, this list of conditions and the following
|
|
|
|
|
disclaimer in the documentation and/or other materials
|
|
|
|
|
provided with the distribution.
|
|
|
|
|
|
|
|
|
|
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER “AS IS” AND ANY
|
|
|
|
|
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
|
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
|
|
|
|
|
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE
|
|
|
|
|
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
|
|
|
|
|
OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
|
|
|
|
|
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
|
|
|
|
|
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
|
|
|
|
|
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
|
|
|
|
|
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
|
|
|
|
|
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
|
SUCH DAMAGE.
|
|
|
|
|
|
|
|
|
|
***********************************************************************/
|
|
|
|
|
|
|
|
|
|
"use strict";
|
|
|
|
|
|
2017-04-15 15:50:50 +00:00
|
|
|
function find_builtins(reserved) {
|
2017-04-03 04:31:05 +00:00
|
|
|
// NaN will be included due to Number.NaN
|
2017-04-15 15:50:50 +00:00
|
|
|
[
|
2017-04-03 19:50:19 +00:00
|
|
|
"null",
|
|
|
|
|
"true",
|
|
|
|
|
"false",
|
2017-04-03 04:31:05 +00:00
|
|
|
"Infinity",
|
2017-04-03 15:17:47 +00:00
|
|
|
"-Infinity",
|
2017-04-03 04:31:05 +00:00
|
|
|
"undefined",
|
2017-04-15 15:50:50 +00:00
|
|
|
].forEach(add);
|
2018-07-26 08:35:43 +00:00
|
|
|
[
|
|
|
|
|
Array,
|
|
|
|
|
Boolean,
|
|
|
|
|
Date,
|
|
|
|
|
Error,
|
|
|
|
|
Function,
|
|
|
|
|
Math,
|
|
|
|
|
Number,
|
|
|
|
|
Object,
|
|
|
|
|
RegExp,
|
|
|
|
|
String,
|
2018-06-06 09:50:56 +00:00
|
|
|
].forEach(function(ctor) {
|
Add property name mangler
We only touch properties that are present in an object literal, or which are
assigned to. Example:
x = { foo: 1 };
x.bar = 2;
x["baz"] = 3;
x[cond ? "qwe" : "asd"] = 4;
console.log(x.stuff);
The names "foo", "bar", "baz", "qwe" and "asd" will be mangled, and the
resulting mangled names will be used for the same properties throughout the
code. The "stuff" will not be, since it's just referenced but never
assigned to.
This *will* break most of the code out there, but could work on carefully
written code: do not use eval, do not define methods or properties by
walking an array of names, etc. Also, a comprehensive list of exclusions
needs to be passed, to avoid mangling properties that are standard in
JavaScript, DOM, used in external libraries etc.
2015-03-14 09:22:28 +00:00
|
|
|
Object.getOwnPropertyNames(ctor).map(add);
|
|
|
|
|
if (ctor.prototype) {
|
|
|
|
|
Object.getOwnPropertyNames(ctor.prototype).map(add);
|
|
|
|
|
}
|
|
|
|
|
});
|
2018-07-26 08:35:43 +00:00
|
|
|
|
Add property name mangler
We only touch properties that are present in an object literal, or which are
assigned to. Example:
x = { foo: 1 };
x.bar = 2;
x["baz"] = 3;
x[cond ? "qwe" : "asd"] = 4;
console.log(x.stuff);
The names "foo", "bar", "baz", "qwe" and "asd" will be mangled, and the
resulting mangled names will be used for the same properties throughout the
code. The "stuff" will not be, since it's just referenced but never
assigned to.
This *will* break most of the code out there, but could work on carefully
written code: do not use eval, do not define methods or properties by
walking an array of names, etc. Also, a comprehensive list of exclusions
needs to be passed, to avoid mangling properties that are standard in
JavaScript, DOM, used in external libraries etc.
2015-03-14 09:22:28 +00:00
|
|
|
function add(name) {
|
2017-04-15 15:50:50 +00:00
|
|
|
push_uniq(reserved, name);
|
Add property name mangler
We only touch properties that are present in an object literal, or which are
assigned to. Example:
x = { foo: 1 };
x.bar = 2;
x["baz"] = 3;
x[cond ? "qwe" : "asd"] = 4;
console.log(x.stuff);
The names "foo", "bar", "baz", "qwe" and "asd" will be mangled, and the
resulting mangled names will be used for the same properties throughout the
code. The "stuff" will not be, since it's just referenced but never
assigned to.
This *will* break most of the code out there, but could work on carefully
written code: do not use eval, do not define methods or properties by
walking an array of names, etc. Also, a comprehensive list of exclusions
needs to be passed, to avoid mangling properties that are standard in
JavaScript, DOM, used in external libraries etc.
2015-03-14 09:22:28 +00:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2017-07-29 15:02:04 +00:00
|
|
|
function reserve_quoted_keys(ast, reserved) {
|
|
|
|
|
ast.walk(new TreeWalker(function(node) {
|
|
|
|
|
if (node instanceof AST_ObjectKeyVal && node.quote) {
|
|
|
|
|
add(node.key);
|
|
|
|
|
} else if (node instanceof AST_Sub) {
|
|
|
|
|
addStrings(node.property, add);
|
|
|
|
|
}
|
|
|
|
|
}));
|
2018-07-26 08:35:43 +00:00
|
|
|
|
|
|
|
|
function add(name) {
|
|
|
|
|
push_uniq(reserved, name);
|
|
|
|
|
}
|
2017-07-29 15:02:04 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
function addStrings(node, add) {
|
|
|
|
|
node.walk(new TreeWalker(function(node) {
|
|
|
|
|
if (node instanceof AST_Sequence) {
|
2017-11-30 19:40:46 +00:00
|
|
|
addStrings(node.tail_node(), add);
|
2017-07-29 15:02:04 +00:00
|
|
|
} else if (node instanceof AST_String) {
|
|
|
|
|
add(node.value);
|
|
|
|
|
} else if (node instanceof AST_Conditional) {
|
|
|
|
|
addStrings(node.consequent, add);
|
|
|
|
|
addStrings(node.alternative, add);
|
|
|
|
|
}
|
|
|
|
|
return true;
|
|
|
|
|
}));
|
|
|
|
|
}
|
|
|
|
|
|
Add property name mangler
We only touch properties that are present in an object literal, or which are
assigned to. Example:
x = { foo: 1 };
x.bar = 2;
x["baz"] = 3;
x[cond ? "qwe" : "asd"] = 4;
console.log(x.stuff);
The names "foo", "bar", "baz", "qwe" and "asd" will be mangled, and the
resulting mangled names will be used for the same properties throughout the
code. The "stuff" will not be, since it's just referenced but never
assigned to.
This *will* break most of the code out there, but could work on carefully
written code: do not use eval, do not define methods or properties by
walking an array of names, etc. Also, a comprehensive list of exclusions
needs to be passed, to avoid mangling properties that are standard in
JavaScript, DOM, used in external libraries etc.
2015-03-14 09:22:28 +00:00
|
|
|
function mangle_properties(ast, options) {
|
|
|
|
|
options = defaults(options, {
|
2017-04-15 15:50:50 +00:00
|
|
|
builtins: false,
|
2017-03-31 08:41:04 +00:00
|
|
|
cache: null,
|
|
|
|
|
debug: false,
|
2017-04-15 15:50:50 +00:00
|
|
|
keep_quoted: false,
|
2017-03-31 08:41:04 +00:00
|
|
|
only_cache: false,
|
|
|
|
|
regex: null,
|
|
|
|
|
reserved: null,
|
2017-07-15 15:50:27 +00:00
|
|
|
}, true);
|
Add property name mangler
We only touch properties that are present in an object literal, or which are
assigned to. Example:
x = { foo: 1 };
x.bar = 2;
x["baz"] = 3;
x[cond ? "qwe" : "asd"] = 4;
console.log(x.stuff);
The names "foo", "bar", "baz", "qwe" and "asd" will be mangled, and the
resulting mangled names will be used for the same properties throughout the
code. The "stuff" will not be, since it's just referenced but never
assigned to.
This *will* break most of the code out there, but could work on carefully
written code: do not use eval, do not define methods or properties by
walking an array of names, etc. Also, a comprehensive list of exclusions
needs to be passed, to avoid mangling properties that are standard in
JavaScript, DOM, used in external libraries etc.
2015-03-14 09:22:28 +00:00
|
|
|
|
2017-06-08 20:29:12 +00:00
|
|
|
var reserved = options.reserved;
|
|
|
|
|
if (!Array.isArray(reserved)) reserved = [];
|
2017-04-15 15:50:50 +00:00
|
|
|
if (!options.builtins) find_builtins(reserved);
|
Add property name mangler
We only touch properties that are present in an object literal, or which are
assigned to. Example:
x = { foo: 1 };
x.bar = 2;
x["baz"] = 3;
x[cond ? "qwe" : "asd"] = 4;
console.log(x.stuff);
The names "foo", "bar", "baz", "qwe" and "asd" will be mangled, and the
resulting mangled names will be used for the same properties throughout the
code. The "stuff" will not be, since it's just referenced but never
assigned to.
This *will* break most of the code out there, but could work on carefully
written code: do not use eval, do not define methods or properties by
walking an array of names, etc. Also, a comprehensive list of exclusions
needs to be passed, to avoid mangling properties that are standard in
JavaScript, DOM, used in external libraries etc.
2015-03-14 09:22:28 +00:00
|
|
|
|
2018-01-04 21:08:09 +00:00
|
|
|
var cname = -1;
|
|
|
|
|
var cache;
|
|
|
|
|
if (options.cache) {
|
|
|
|
|
cache = options.cache.props;
|
|
|
|
|
cache.each(function(mangled_name) {
|
|
|
|
|
push_uniq(reserved, mangled_name);
|
|
|
|
|
});
|
|
|
|
|
} else {
|
|
|
|
|
cache = new Dictionary();
|
Add property name mangler
We only touch properties that are present in an object literal, or which are
assigned to. Example:
x = { foo: 1 };
x.bar = 2;
x["baz"] = 3;
x[cond ? "qwe" : "asd"] = 4;
console.log(x.stuff);
The names "foo", "bar", "baz", "qwe" and "asd" will be mangled, and the
resulting mangled names will be used for the same properties throughout the
code. The "stuff" will not be, since it's just referenced but never
assigned to.
This *will* break most of the code out there, but could work on carefully
written code: do not use eval, do not define methods or properties by
walking an array of names, etc. Also, a comprehensive list of exclusions
needs to be passed, to avoid mangling properties that are standard in
JavaScript, DOM, used in external libraries etc.
2015-03-14 09:22:28 +00:00
|
|
|
}
|
|
|
|
|
|
2015-06-09 10:21:22 +00:00
|
|
|
var regex = options.regex;
|
|
|
|
|
|
2016-10-27 15:23:04 +00:00
|
|
|
// note debug is either false (disabled), or a string of the debug suffix to use (enabled).
|
|
|
|
|
// note debug may be enabled as an empty string, which is falsey. Also treat passing 'true'
|
|
|
|
|
// the same as passing an empty string.
|
2017-04-15 15:50:50 +00:00
|
|
|
var debug = options.debug !== false;
|
2018-07-26 08:35:43 +00:00
|
|
|
var debug_suffix;
|
|
|
|
|
if (debug) debug_suffix = options.debug === true ? "" : options.debug;
|
2016-10-27 15:23:04 +00:00
|
|
|
|
Add property name mangler
We only touch properties that are present in an object literal, or which are
assigned to. Example:
x = { foo: 1 };
x.bar = 2;
x["baz"] = 3;
x[cond ? "qwe" : "asd"] = 4;
console.log(x.stuff);
The names "foo", "bar", "baz", "qwe" and "asd" will be mangled, and the
resulting mangled names will be used for the same properties throughout the
code. The "stuff" will not be, since it's just referenced but never
assigned to.
This *will* break most of the code out there, but could work on carefully
written code: do not use eval, do not define methods or properties by
walking an array of names, etc. Also, a comprehensive list of exclusions
needs to be passed, to avoid mangling properties that are standard in
JavaScript, DOM, used in external libraries etc.
2015-03-14 09:22:28 +00:00
|
|
|
var names_to_mangle = [];
|
2015-07-31 13:56:33 +00:00
|
|
|
var unmangleable = [];
|
Add property name mangler
We only touch properties that are present in an object literal, or which are
assigned to. Example:
x = { foo: 1 };
x.bar = 2;
x["baz"] = 3;
x[cond ? "qwe" : "asd"] = 4;
console.log(x.stuff);
The names "foo", "bar", "baz", "qwe" and "asd" will be mangled, and the
resulting mangled names will be used for the same properties throughout the
code. The "stuff" will not be, since it's just referenced but never
assigned to.
This *will* break most of the code out there, but could work on carefully
written code: do not use eval, do not define methods or properties by
walking an array of names, etc. Also, a comprehensive list of exclusions
needs to be passed, to avoid mangling properties that are standard in
JavaScript, DOM, used in external libraries etc.
2015-03-14 09:22:28 +00:00
|
|
|
|
|
|
|
|
// step 1: find candidates to mangle
|
2018-06-06 09:50:56 +00:00
|
|
|
ast.walk(new TreeWalker(function(node) {
|
Add property name mangler
We only touch properties that are present in an object literal, or which are
assigned to. Example:
x = { foo: 1 };
x.bar = 2;
x["baz"] = 3;
x[cond ? "qwe" : "asd"] = 4;
console.log(x.stuff);
The names "foo", "bar", "baz", "qwe" and "asd" will be mangled, and the
resulting mangled names will be used for the same properties throughout the
code. The "stuff" will not be, since it's just referenced but never
assigned to.
This *will* break most of the code out there, but could work on carefully
written code: do not use eval, do not define methods or properties by
walking an array of names, etc. Also, a comprehensive list of exclusions
needs to be passed, to avoid mangling properties that are standard in
JavaScript, DOM, used in external libraries etc.
2015-03-14 09:22:28 +00:00
|
|
|
if (node instanceof AST_ObjectKeyVal) {
|
2017-07-29 15:02:04 +00:00
|
|
|
add(node.key);
|
2018-07-26 08:35:43 +00:00
|
|
|
} else if (node instanceof AST_ObjectProperty) {
|
Add property name mangler
We only touch properties that are present in an object literal, or which are
assigned to. Example:
x = { foo: 1 };
x.bar = 2;
x["baz"] = 3;
x[cond ? "qwe" : "asd"] = 4;
console.log(x.stuff);
The names "foo", "bar", "baz", "qwe" and "asd" will be mangled, and the
resulting mangled names will be used for the same properties throughout the
code. The "stuff" will not be, since it's just referenced but never
assigned to.
This *will* break most of the code out there, but could work on carefully
written code: do not use eval, do not define methods or properties by
walking an array of names, etc. Also, a comprehensive list of exclusions
needs to be passed, to avoid mangling properties that are standard in
JavaScript, DOM, used in external libraries etc.
2015-03-14 09:22:28 +00:00
|
|
|
// setter or getter, since KeyVal is handled above
|
|
|
|
|
add(node.key.name);
|
2018-07-26 08:35:43 +00:00
|
|
|
} else if (node instanceof AST_Dot) {
|
2016-07-31 06:35:14 +00:00
|
|
|
add(node.property);
|
2018-07-26 08:35:43 +00:00
|
|
|
} else if (node instanceof AST_Sub) {
|
2017-07-29 15:02:04 +00:00
|
|
|
addStrings(node.property, add);
|
2018-07-26 08:35:43 +00:00
|
|
|
} else if (node instanceof AST_Call
|
2018-04-06 09:10:36 +00:00
|
|
|
&& node.expression.print_to_string() == "Object.defineProperty") {
|
|
|
|
|
addStrings(node.args[1], add);
|
|
|
|
|
}
|
Add property name mangler
We only touch properties that are present in an object literal, or which are
assigned to. Example:
x = { foo: 1 };
x.bar = 2;
x["baz"] = 3;
x[cond ? "qwe" : "asd"] = 4;
console.log(x.stuff);
The names "foo", "bar", "baz", "qwe" and "asd" will be mangled, and the
resulting mangled names will be used for the same properties throughout the
code. The "stuff" will not be, since it's just referenced but never
assigned to.
This *will* break most of the code out there, but could work on carefully
written code: do not use eval, do not define methods or properties by
walking an array of names, etc. Also, a comprehensive list of exclusions
needs to be passed, to avoid mangling properties that are standard in
JavaScript, DOM, used in external libraries etc.
2015-03-14 09:22:28 +00:00
|
|
|
}));
|
|
|
|
|
|
|
|
|
|
// step 2: transform the tree, renaming properties
|
2018-06-06 09:50:56 +00:00
|
|
|
return ast.transform(new TreeTransformer(function(node) {
|
Add property name mangler
We only touch properties that are present in an object literal, or which are
assigned to. Example:
x = { foo: 1 };
x.bar = 2;
x["baz"] = 3;
x[cond ? "qwe" : "asd"] = 4;
console.log(x.stuff);
The names "foo", "bar", "baz", "qwe" and "asd" will be mangled, and the
resulting mangled names will be used for the same properties throughout the
code. The "stuff" will not be, since it's just referenced but never
assigned to.
This *will* break most of the code out there, but could work on carefully
written code: do not use eval, do not define methods or properties by
walking an array of names, etc. Also, a comprehensive list of exclusions
needs to be passed, to avoid mangling properties that are standard in
JavaScript, DOM, used in external libraries etc.
2015-03-14 09:22:28 +00:00
|
|
|
if (node instanceof AST_ObjectKeyVal) {
|
2017-07-29 15:02:04 +00:00
|
|
|
node.key = mangle(node.key);
|
2018-07-26 08:35:43 +00:00
|
|
|
} else if (node instanceof AST_ObjectProperty) {
|
Add property name mangler
We only touch properties that are present in an object literal, or which are
assigned to. Example:
x = { foo: 1 };
x.bar = 2;
x["baz"] = 3;
x[cond ? "qwe" : "asd"] = 4;
console.log(x.stuff);
The names "foo", "bar", "baz", "qwe" and "asd" will be mangled, and the
resulting mangled names will be used for the same properties throughout the
code. The "stuff" will not be, since it's just referenced but never
assigned to.
This *will* break most of the code out there, but could work on carefully
written code: do not use eval, do not define methods or properties by
walking an array of names, etc. Also, a comprehensive list of exclusions
needs to be passed, to avoid mangling properties that are standard in
JavaScript, DOM, used in external libraries etc.
2015-03-14 09:22:28 +00:00
|
|
|
// setter or getter
|
2015-07-31 13:56:33 +00:00
|
|
|
node.key.name = mangle(node.key.name);
|
2018-07-26 08:35:43 +00:00
|
|
|
} else if (node instanceof AST_Dot) {
|
2015-07-31 13:56:33 +00:00
|
|
|
node.property = mangle(node.property);
|
2018-07-26 08:35:43 +00:00
|
|
|
} else if (!options.keep_quoted && node instanceof AST_Sub) {
|
2017-07-29 15:02:04 +00:00
|
|
|
node.property = mangleStrings(node.property);
|
2018-07-26 08:35:43 +00:00
|
|
|
} else if (node instanceof AST_Call
|
2018-04-06 09:10:36 +00:00
|
|
|
&& node.expression.print_to_string() == "Object.defineProperty") {
|
|
|
|
|
node.args[1] = mangleStrings(node.args[1]);
|
|
|
|
|
}
|
Add property name mangler
We only touch properties that are present in an object literal, or which are
assigned to. Example:
x = { foo: 1 };
x.bar = 2;
x["baz"] = 3;
x[cond ? "qwe" : "asd"] = 4;
console.log(x.stuff);
The names "foo", "bar", "baz", "qwe" and "asd" will be mangled, and the
resulting mangled names will be used for the same properties throughout the
code. The "stuff" will not be, since it's just referenced but never
assigned to.
This *will* break most of the code out there, but could work on carefully
written code: do not use eval, do not define methods or properties by
walking an array of names, etc. Also, a comprehensive list of exclusions
needs to be passed, to avoid mangling properties that are standard in
JavaScript, DOM, used in external libraries etc.
2015-03-14 09:22:28 +00:00
|
|
|
}));
|
|
|
|
|
|
|
|
|
|
// only function declarations after this line
|
|
|
|
|
|
|
|
|
|
function can_mangle(name) {
|
2015-07-31 13:56:33 +00:00
|
|
|
if (unmangleable.indexOf(name) >= 0) return false;
|
2015-05-07 12:01:16 +00:00
|
|
|
if (reserved.indexOf(name) >= 0) return false;
|
2018-07-26 08:35:43 +00:00
|
|
|
if (options.only_cache) return cache.has(name);
|
2017-04-03 19:50:19 +00:00
|
|
|
if (/^-?[0-9]+(\.[0-9]+)?(e[+-][0-9]+)?$/.test(name)) return false;
|
Add property name mangler
We only touch properties that are present in an object literal, or which are
assigned to. Example:
x = { foo: 1 };
x.bar = 2;
x["baz"] = 3;
x[cond ? "qwe" : "asd"] = 4;
console.log(x.stuff);
The names "foo", "bar", "baz", "qwe" and "asd" will be mangled, and the
resulting mangled names will be used for the same properties throughout the
code. The "stuff" will not be, since it's just referenced but never
assigned to.
This *will* break most of the code out there, but could work on carefully
written code: do not use eval, do not define methods or properties by
walking an array of names, etc. Also, a comprehensive list of exclusions
needs to be passed, to avoid mangling properties that are standard in
JavaScript, DOM, used in external libraries etc.
2015-03-14 09:22:28 +00:00
|
|
|
return true;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
function should_mangle(name) {
|
2015-06-09 10:21:22 +00:00
|
|
|
if (regex && !regex.test(name)) return false;
|
2015-05-13 19:03:00 +00:00
|
|
|
if (reserved.indexOf(name) >= 0) return false;
|
2018-07-26 08:35:43 +00:00
|
|
|
return cache.has(name) || names_to_mangle.indexOf(name) >= 0;
|
Add property name mangler
We only touch properties that are present in an object literal, or which are
assigned to. Example:
x = { foo: 1 };
x.bar = 2;
x["baz"] = 3;
x[cond ? "qwe" : "asd"] = 4;
console.log(x.stuff);
The names "foo", "bar", "baz", "qwe" and "asd" will be mangled, and the
resulting mangled names will be used for the same properties throughout the
code. The "stuff" will not be, since it's just referenced but never
assigned to.
This *will* break most of the code out there, but could work on carefully
written code: do not use eval, do not define methods or properties by
walking an array of names, etc. Also, a comprehensive list of exclusions
needs to be passed, to avoid mangling properties that are standard in
JavaScript, DOM, used in external libraries etc.
2015-03-14 09:22:28 +00:00
|
|
|
}
|
|
|
|
|
|
2017-07-29 15:02:04 +00:00
|
|
|
function add(name) {
|
2018-07-26 08:35:43 +00:00
|
|
|
if (can_mangle(name)) push_uniq(names_to_mangle, name);
|
|
|
|
|
if (!should_mangle(name)) push_uniq(unmangleable, name);
|
Add property name mangler
We only touch properties that are present in an object literal, or which are
assigned to. Example:
x = { foo: 1 };
x.bar = 2;
x["baz"] = 3;
x[cond ? "qwe" : "asd"] = 4;
console.log(x.stuff);
The names "foo", "bar", "baz", "qwe" and "asd" will be mangled, and the
resulting mangled names will be used for the same properties throughout the
code. The "stuff" will not be, since it's just referenced but never
assigned to.
This *will* break most of the code out there, but could work on carefully
written code: do not use eval, do not define methods or properties by
walking an array of names, etc. Also, a comprehensive list of exclusions
needs to be passed, to avoid mangling properties that are standard in
JavaScript, DOM, used in external libraries etc.
2015-03-14 09:22:28 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
function mangle(name) {
|
2015-07-31 13:56:33 +00:00
|
|
|
if (!should_mangle(name)) {
|
|
|
|
|
return name;
|
|
|
|
|
}
|
2018-01-04 21:08:09 +00:00
|
|
|
var mangled = cache.get(name);
|
Add property name mangler
We only touch properties that are present in an object literal, or which are
assigned to. Example:
x = { foo: 1 };
x.bar = 2;
x["baz"] = 3;
x[cond ? "qwe" : "asd"] = 4;
console.log(x.stuff);
The names "foo", "bar", "baz", "qwe" and "asd" will be mangled, and the
resulting mangled names will be used for the same properties throughout the
code. The "stuff" will not be, since it's just referenced but never
assigned to.
This *will* break most of the code out there, but could work on carefully
written code: do not use eval, do not define methods or properties by
walking an array of names, etc. Also, a comprehensive list of exclusions
needs to be passed, to avoid mangling properties that are standard in
JavaScript, DOM, used in external libraries etc.
2015-03-14 09:22:28 +00:00
|
|
|
if (!mangled) {
|
2016-10-27 15:23:04 +00:00
|
|
|
if (debug) {
|
|
|
|
|
// debug mode: use a prefix and suffix to preserve readability, e.g. o.foo -> o._$foo$NNN_.
|
2018-07-26 08:35:43 +00:00
|
|
|
var debug_mangled = "_$" + name + "$" + debug_suffix + "_";
|
|
|
|
|
if (can_mangle(debug_mangled)) mangled = debug_mangled;
|
2016-10-27 15:23:04 +00:00
|
|
|
}
|
|
|
|
|
// either debug mode is off, or it is on and we could not use the mangled name
|
2018-07-26 08:35:43 +00:00
|
|
|
if (!mangled) do {
|
|
|
|
|
mangled = base54(++cname);
|
|
|
|
|
} while (!can_mangle(mangled));
|
2018-01-04 21:08:09 +00:00
|
|
|
cache.set(name, mangled);
|
Add property name mangler
We only touch properties that are present in an object literal, or which are
assigned to. Example:
x = { foo: 1 };
x.bar = 2;
x["baz"] = 3;
x[cond ? "qwe" : "asd"] = 4;
console.log(x.stuff);
The names "foo", "bar", "baz", "qwe" and "asd" will be mangled, and the
resulting mangled names will be used for the same properties throughout the
code. The "stuff" will not be, since it's just referenced but never
assigned to.
This *will* break most of the code out there, but could work on carefully
written code: do not use eval, do not define methods or properties by
walking an array of names, etc. Also, a comprehensive list of exclusions
needs to be passed, to avoid mangling properties that are standard in
JavaScript, DOM, used in external libraries etc.
2015-03-14 09:22:28 +00:00
|
|
|
}
|
|
|
|
|
return mangled;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
function mangleStrings(node) {
|
2018-06-06 09:50:56 +00:00
|
|
|
return node.transform(new TreeTransformer(function(node) {
|
2017-04-12 13:56:27 +00:00
|
|
|
if (node instanceof AST_Sequence) {
|
|
|
|
|
var last = node.expressions.length - 1;
|
|
|
|
|
node.expressions[last] = mangleStrings(node.expressions[last]);
|
2018-07-26 08:35:43 +00:00
|
|
|
} else if (node instanceof AST_String) {
|
2015-07-31 13:56:33 +00:00
|
|
|
node.value = mangle(node.value);
|
2018-07-26 08:35:43 +00:00
|
|
|
} else if (node instanceof AST_Conditional) {
|
Add property name mangler
We only touch properties that are present in an object literal, or which are
assigned to. Example:
x = { foo: 1 };
x.bar = 2;
x["baz"] = 3;
x[cond ? "qwe" : "asd"] = 4;
console.log(x.stuff);
The names "foo", "bar", "baz", "qwe" and "asd" will be mangled, and the
resulting mangled names will be used for the same properties throughout the
code. The "stuff" will not be, since it's just referenced but never
assigned to.
This *will* break most of the code out there, but could work on carefully
written code: do not use eval, do not define methods or properties by
walking an array of names, etc. Also, a comprehensive list of exclusions
needs to be passed, to avoid mangling properties that are standard in
JavaScript, DOM, used in external libraries etc.
2015-03-14 09:22:28 +00:00
|
|
|
node.consequent = mangleStrings(node.consequent);
|
|
|
|
|
node.alternative = mangleStrings(node.alternative);
|
|
|
|
|
}
|
|
|
|
|
return node;
|
|
|
|
|
}));
|
|
|
|
|
}
|
|
|
|
|
}
|