Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
eslint-plugin-no-iife
Advanced tools
An eslint plugin to prevent immediately-invoked function expression (IIFE) usage in your code.
npm install --save-dev eslint-plugin-no-iife
In your .eslintrc
(or wherever your eslint configuration lives):
{
"plugins": [
"no-iife"
],
"rules": {
"no-iife/no-iife": "error"
}
}
This rule prevents all immediately-invoked function expressions.
Immediately-invoked function expressions are a messy remnant of early Javascript, and their use today only serves to decrease readability. They can and should be entirely replaced with modern syntax.
Historically, the IIFE had two main advantages. First, it served as a shorthand for calling a function which was just defined. While this pattern can lead to convoluted code, there are a handful of legitimate reasons to call code immediately after definition, such as factory functions. However, it is much more human-readable to define a function and then call it in the next statement. Compare this IIFE:
const x = (function() {
return function() {
foo();
}
})();
With this version:
const y = function() {
return function() {
foo();
}
};
const x = y();
The other use-case for IIFEs was much more practical; imposing a limited scope.
The problem arises from var
, which hoists variables to the top of the function
scope. In a top-level script, the function scope is global, making all the
variables global. And since var
variables can be reassigned with another use
of var
, it's all too easy to override existing globals. Besides, having so
many global variables makes debugging far more difficult.
IIFEs solve this problem by wrapping a script in an anonymous function, limiting the scope to just one page (or less). This was a savior for many common problems, but at the cost of being messy and confusing.
In modern Javascript, however, var
is rarely used, and so the problem of
global variable pollution has entirely disappeared. By using const
and let
,
there is simply no need for IIFEs anymore.
Copyright (c) 2019 Jade Michael Thornton
Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
FAQs
Prevents IIFE usage
The npm package eslint-plugin-no-iife receives a total of 2 weekly downloads. As such, eslint-plugin-no-iife popularity was classified as not popular.
We found that eslint-plugin-no-iife demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.