I'm having a depreciation warning on using the LTS version of node@22.11.0 and bcrypt@5.1.1

[sicktooth]

• What went wrong?

• I'm having a depreciation warning on using the LTS version of node@22.11.0 and bcrypt@5.1.1

• What did you expect to happen?

• no warning

• Which version of nodejs and OS?

• node@22.11.0 OS@10.0.19044 Build 19044

• If you find a bug, please write a failing test.

• $ npm i bcrypt
  npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memo
  ry. Do not use it. Check out lru-cache if you want a good and tested way to coal
  esce async requests by a key value, which is much more comprehensive and powerfu
  l.
  npm warn deprecated npmlog@5.0.1: This package is no longer supported.
  npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supp
  orted
  npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supporte
  d
  npm warn deprecated are-we-there-yet@2.0.0: This package is no longer supported.
  npm warn deprecated gauge@3.0.2: This package is no longer supported.

added 55 packages, and audited 174 packages in 14s

22 packages are looking for funding
run npm fund for details

found 0 vulnerabilities

[minenwerfer]

Same here. It seems the version that replaces the deprecated @mapbox/node-pre-gyp dependency with prebuildify was committed 1 year ago but was never released.

[sicktooth]

so it's nothing to worry about I guess..

[grandgeorg]

I get the same warnings, running NodeJS v18.20.1 and npm v10.9.0.
Nothing to worry about? - IMHO: When a component of your security package says " This module is not supported, and leaks memory. Do not use it." you should be worried!