Investigation: is-number

[43081j]

Just notes for how we can tackle this one.

Of course, typeof obj === 'number' will be fine for most consumers

there may be edge cases where this package is necessary, but most likely it belongs in edge cases rather than the common case.

Significant dependents

• to-regex-range
• randomatic - replace with nanoid
• get-object - replace with dlv
• array-initial - replace with slice(start, -1)
• array-last - replace with slice(-offset)
• window-size - probably somewhat useful still

Highest impact chain

to-regex-range is the key here. The primary path is:

• braces
  • fill-range
    • to-regex-range
      • is-number

The first primary package we reach is braces, a package for bash-like brace expansion.

We can probably replace braces with brace-expansion.

Some significant consumers of braces are:

• chokidar
• karma
• wireit

If we move these to use brace-expansion (or any other light alternative we can agree on), we will likely strip is-number from most of the common dependency trees.

[mehulkar]

I took a random stab at this today and replaced wireit's brace with brace-extension. The main thing that came up is wireit has a transitive dependency on micromatch (via @11ty/eleventy and fast-glob), and micromatch depends on braces, so braces is still in the tree

[43081j]

ultimately i wonder if we could have a fast-glob alternative thats faster and lighter, an issue for another time though

even if we still have braces in wireit's tree, we're making progress 👍

[mehulkar]

another fast-glob alternative could be fdir (discovered here: 11ty/eleventy#3167) or the upcoming fs.glob native API

[43081j]

great find 🙏

IMO we should migrate towards fdir and, once the native API settles, consider using that in projects which don't need to support older node versions