Use of deprecated glob and rimraf dependencies

[jwasnoggin]

When installing nyc there are a number of npm warnings about deprecated packages:

$ npm i -D nyc 
npm WARN deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported

It looks like glob is only used in tests, so maybe this should be moved to devDependencies?

Usages of rimraf will need to be modified slightly but this doesn't look too onerous.

inflight is only used as a dependency of the other two.

Environment Information

  System:
    OS: Linux 6.8 Fedora Linux 38 (Workstation Edition)
    CPU: (8) x64 Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz
    Memory: 3.95 GB / 15.46 GB
  Binaries:
    Node: 20.10.0 - ~/.nvm/versions/node/v20.10.0/bin/node
    npm: 10.2.3 - ~/.nvm/versions/node/v20.10.0/bin/npm
  npmPackages:
    nyc: ^15.1.0 => 15.1.0 
    ts-node: ^10.9.2 => 10.9.2 
    typescript: ^5.4.5 => 5.4.5 

[DinoChiesa]

It's complicated. rimraf is used directly by nyc, but also in various modules that are dependencies of nyc. Including istanbul-lib-processinfo, which itself has a devDependency on nyc.

$ npm list rimraf
[email protected] /Users/dev/istanbuljs/nyc
├─┬ [email protected]
│ └── [email protected] deduped
├── [email protected]
├─┬ [email protected]
│ └── [email protected] deduped
├─┬ [email protected]
│ └─┬ [email protected]
│   └─┬ [email protected]
│     └─┬ [email protected]
│       └── [email protected]
└─┬ [email protected]
  ├─┬ @tapjs/[email protected]
  │ └── [email protected]
  ├─┬ @tapjs/[email protected]
  │ ├─┬ [email protected]
  │ │ └── [email protected] deduped
  │ └── [email protected]
  └─┬ @tapjs/[email protected]
    ├── [email protected]
    ├─┬ [email protected]
    │ └── [email protected]
    └─┬ [email protected]
      └── [email protected]

So basically you have a hairball to untangle here.