Deprecated Packages in n8n Update

Describe the problem/error/question

I recently ran sudo npm update -g n8n to update n8n globally, and I encountered several warnings about deprecated packages. It seems that some of the dependencies in n8n are outdated or have been moved to newer packages. I’m wondering if anyone else has seen this and if there are any updates planned to resolve these warnings.

What is the error message (if any)?

npm warn deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs
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 @aws-sdk/[email protected]: This package has moved to @smithy/signature-v4
npm warn deprecated [email protected]: Package is no longer maintained
...

Please share your workflow

N/A (The issue occurs during the update process, not with a specific workflow.)

Share the output returned by the last node

N/A (The issue occurs during the update process, not with a specific workflow.)

Information on your n8n setup

  • n8n version: (provide your current version, e.g., 0.200.0)
  • Database (default: SQLite): (e.g., SQLite, MySQL, PostgreSQL)
  • n8n EXECUTIONS_PROCESS setting (default: own, main): (e.g., own)
  • Running n8n via (Docker, npm, n8n cloud, desktop app): (e.g., npm)
  • Operating system: (e.g., Ubuntu 20.04)

These packages aren’t directly used by n8n, and are actually transitive dependencies used deep down in the dependency tree.
We can’t address these ourselves, and depend on 3rd party package maintainers to address these.
For example @npmcli/[email protected] comes from:

sqlite3 5.1.7
└─┬ node-gyp 8.4.1
  └─┬ make-fetch-happen 9.1.0
    └─┬ cacache 15.3.0
      └── @npmcli/move-file 1.1.2

There are multiple PRs on the sqlite3 repo to upgrade node-gyp, that would fix this issue, but they seem to have gone unnoticed so far.

It’s similar story for most of the other deprecated packages as well.
There isn’t much n8n can do besides waiting for individual package maintainers to upgrade their dependency tree.