No DB entries when installing community nodes manually

We recently upgraded from 0.163 to the current version. I noticed that the new possibility to use the UI to install community nodes not only updates the package.json in ~/.n8n/nodes, but also the tables installed_nodes and installed_packages in the n8n database.
However, this does not happen when running npm i in the ~/.n8n/nodes directory. The installed node runs, but I cannot find it under Settings → Community Nodes.
Are there any other consequences resulting from the tables not being filled?

Update: Same behavior on docker

  • n8n version:: v1.20
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): npm
  • Operating system:: Mac Ventura

Hey @lorenz,

Welcome to the community :raised_hands:

We only track in the UI and in the database nodes that have been installed from the n8n UI. You can still install nodes outside of n8n like you currently have but you won’t be able to update them or manage them from inside n8n.