The NPM ecosystem is cluttered with unnecessary packages like is-odd, is-even, is-number, and more. We don’t need this unnecessary clutter.

Ever heard of the is-number? It’s an infamous NPM package that simply checks if a value is a number or not.

1
import isNumber from 'is-number';

I checked out the is-number package and here’s what it actually does.

1
module.exports = function(num) {
2
  if (typeof num === 'number') {
3
    return num - num === 0;
4
  }
5
  if (typeof num === 'string' && num.trim() !== '') {
6
    return Number.isFinite ? Number.isFinite(+num) : isFinite(+num);
7
  }
8
  return false;
9
};

If only there were a built-in method to check if something is a number. Oh, wait… there is.

1
const number = 5;
2
typeof number === "number" && Number.isFinite(number); // true

1. typeof num === ‘number’: Verifies that num is of the type “number”. This excludes other data types like strings, objects, etc.

2. Number.isFinite(num): Ensures that num is a finite number, meaning it is not NaN, Infinity, or -Infinity.

Infinity, -Infinity, and NaN are all considered numbers in JavaScript, so typeof returns ‘number’ for each of them. Thus, these statements are true.

1
typeof Infinity === 'number';  // true
2
typeof -Infinity === 'number'; // true
3
typeof NaN === 'number';       // true

While typeof returns true for each of these values, Number.isFinite returns false because Infinity, -Infinity, and NaN are not finite numbers. Therefore, the combined expressions using && evaluate to false.

1
typeof Infinity === "number" && Number.isFinite(Infinity); // false
2
typeof -Infinity === "number" && Number.isFinite(-Infinity); // false
3
typeof NaN === "number" && Number.isFinite(NaN); // false

Both 5 and -5 are valid, finite numbers, so both expressions are true.

1
typeof 5 === "number" && Number.isFinite(5); //true
2
typeof -5 === "number" && Number.isFinite(-5); // true

Moving back to rubbish packages. How on earth does is-number have 68,049,915 weekly downloads?

I guess it’s likely because is-number is a dependency for many popular libraries and frameworks. Even if you’re not using it directly, it could be included in your project through another package that relies on it.

left-pad package

In 2016, the left-pad package was unexpectedly removed from the npm registry, causing widespread disruption in the JavaScript ecosystem.

Many projects depended on this tiny package for a simple string padding function.

Its removal led to broken builds and errors in numerous projects, highlighting the risks of relying on overly granular or unnecessary dependencies.

The incident underscored the importance of using native functionality whenever possible to avoid such issues. See the left-pad incident wikipedia page.

1
import leftpad from 'left-pad';

Since String.prototype.padStart is a standard part of modern JavaScript, there’s no need to rely on an additional package for this.

1
"left-pad" should be replaced with native functionality. You can instead use String.prototype.padStart.
2

3
Read more here: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/padStarteslintdepend/ban-dependencies

eslint-plugin-depend

This ESLint plugin detects redundant packages and suggests more efficient alternatives.

1
import isNumber from 'is-number';

Would trigger a notification inside the code editor/IDE

1
"is-number" should be replaced with inline/local logic. Use typeof v === "number" || (typeof v === "string" && Number.isFinite(+v)) eslint depend/ban-dependencies

Installing

1
npm i -D eslint-plugin-depend

eslint.config.js

1
import * as depend from 'eslint-plugin-depend';
2

3
export default [
4
  depend.configs['flat/recommended']
5
];

You may choose a preset list of dependencies (or none). The following are available:

1. microutilities: micro utilities (e.g. one liners)
2. native: redundant packages with native equivalents
3. preferred: an opinionated list of packages with better maintained and lighter alternatives

1
{
2
  "rules": {
3
    "depend/ban-dependencies": ["error", {
4
      "presets": ["native"]
5
    }]
6
  }
7
}

The default is [‘native’, ‘microutilities’, ‘preferred’].

modules: You may specify your own list of packages which will be disallowed in code.

1
{
2
  "rules": {
3
    "depend/ban-dependencies": ["error", {
4
      "modules": ["im-a-banned-package"]
5
    }]
6
  }
7
}

Putting it together

1
import * as depend from 'eslint-plugin-depend';
2

3
export default [
4
  depend.configs['flat/recommended'],
5
  {
6
    rules: {
7
      "depend/ban-dependencies": ["error", {
8
        presets: ["native"],
9
        modules: ["im-a-banned-package"]
10
      }]
11
    }
12
  }
13
];

Trim the fat, clear out the clutter, and let your code breathe. Your users will thank you for it.