Usage of
strict mode against recommended approach JS-0118
Bug risk
Minor
5 months ago
—
2 years old
Prefer using strict mode in the global scope
11896 */
11897
11898(function ($, Drupal) {
11899 "use strict";11900
11901 Drupal.behaviors.modifiers = {
11902 attach: function attach(context, settings) {Prefer using strict mode in the global scope
11379 */
11380
11381(function ($, Drupal) {
11382 "use strict";11383
11384 /**
11385 * Adds check all or none checkboxes support.Prefer using strict mode in the global scope
11351 */
11352
11353(function ($, Drupal) {
11354 "use strict";11355
11356 /**
11357 * Attach handlers to options buttons element.Prefer using strict mode in the global scope
10498 })
10499 : r(jQuery);
10500})(function (q) {
10501 "use strict";10502 var m = /\r?\n/g,
10503 S = {};
10504 (S.fileapi = void 0 !== q('<input type="file">').get(0).files),Prefer using strict mode in the global scope
10333 */
10334
10335(function ($, Drupal) {
10336 "use strict";10337
10338 // Determine if local storage exists and is enabled.
10339 // This approach is copied from Modernizr.
Description
A strict mode directive is a "use strict" literal at the beginning of a script or function body. It enables strict mode semantics.
When a directive occurs in global scope, strict mode applies to the entire script:
"use strict";
// strict mode
function foo() {
// strict mode
}
When a directive occurs at the beginning of a function body, strict mode applies only to that function, including all contained functions:
function foo() {
"use strict";
// strict mode
}
function foo2() {
// not strict mode
};
(function() {
"use strict";
function bar() {
// strict mode
}
}());
In the CommonJS module system, a hidden function wraps each module and limits the scope of a "global" strict mode directive.
In ECMAScript modules, which always have strict mode semantics, the directives are unnecessary.
Bad Practice
function foo() {
}
function foo() {
"use strict";
}
"use strict";
function foo() {
"use strict";
}
Recommended
function foo() {
}