On installation, npm prints many warnings of stale dependencies

[robogeek]

Issue Summary

I've just added sqlite3 to my project, it is using version 5.1.7 (the latest as of this writing), and I get these warnings:

$ npm install
npm warn deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs
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]: This package is no longer supported.
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: This package is 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
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: This package is no longer supported.

I try to keep my project clean of these type of warnings. All of them trace back to an old node-gyp version being used.

For example:

$ npm ls @npmcli/move-file
[email protected] /home/david/Projects/akasharender/akasharender
└─┬ [email protected]
  └─┬ [email protected]
    └─┬ [email protected]
      └─┬ [email protected]
        └── @npmcli/[email protected]

All the other dependencies have a similar output.

I haven't checked if updating node-gyp will fix these stale dependencies. But that would be a good first start. If any remain, then it's a matter of informing the other projects to update their dependencies.

Relevant logs or output

See above

Version

5.1.7

Node.js Version

22.x

How did you install the library?

npm install sqlite3 --save

[andyImatest]

I was able to get rid of these in my project by adding an override in package.json for node-gyp to 10.2.0 and another for glob 11.0.0. Upgrading these didn't seem to affect node-sqlite3 (as far as I can tell. It builds and it works for what I need it to do :) )

"overrides": { "glob": "11.0.0", "node-gyp": "10.2.0" },

[robogeek]

Good to know about this workaround. That would seem to support the idea that the sqlite3 team could bump the dependency version number with little about having to spend months working on upgrading the code. Sounds like it would instead be a 2 minute task.