eval() should not be used JS-0060eval can be harmful
11754 "undefined" != typeof module && (module.exports = AU),
11755 "undefined" != typeof exports &&
11756 (Object.defineProperty(exports, "__esModule", { value: !0 }),
11757 eval("exports.default = AU"));11758var AU = AU || {};
11759!(function (e) {
11760 function n(e, n, t, o) {eval can be harmful
11037 L =
11038 q.parseJSON ||
11039 function (e) {
11040 return window.eval("(" + e + ")");11041 },
11042 E = function (e, t, r) {
11043 var a = e.getResponseHeader("content-type") || "",eval can be harmful
11534 L =
11535 q.parseJSON ||
11536 function (e) {
11537 return window.eval("(" + e + ")");11538 },
11539 E = function (e, t, r) {
11540 var a = e.getResponseHeader("content-type") || "",eval can be harmful
11759 "undefined" != typeof module && (module.exports = AU),
11760 "undefined" != typeof exports &&
11761 (Object.defineProperty(exports, "__esModule", { value: !0 }),
11762 eval("exports.default = AU"));11763/**
11764 * @file
11765 * Initializes all modifications.eval can be harmful
11037 L =
11038 q.parseJSON ||
11039 function (e) {
11040 return window.eval("(" + e + ")");11041 },
11042 E = function (e, t, r) {
11043 var a = e.getResponseHeader("content-type") || "",
Description
JavaScript's eval() function is potentially dangerous and is often misused.
Using eval() on untrusted code can open a program up to several different injection attacks.
The use of eval() in most contexts can be substituted for a better, alternative approach to the problem.
Bad Practice
const obj = { x: "foo" }
const key = "x"
const value = eval("obj." + key);
(0, eval)("var a = 0");
const foo = eval;
foo("var a = 0");
// This `this` is the global object.
this.eval("var a = 0");
Recommended
const obj = { x: "foo" },
key = "x",
value = obj[key];
class A {
foo() {
// This is a user-defined method.
this.eval("var a = 0");
}
eval() { /* ... * / }
}