Next time i have the log i will show you but:
- i'm not in the .node-red folder since nodered is mounted as dependency of my app. and configuration is passed programmatically
- no files are saved on disk at all, since i've implemented a storage plugin to route all the data over a mongodb collection
- the package is not listed in package.json nor package-lock.json after npm uninstall
However i'm noticing that if the package is still listed into the json defined in (the former file who is on db in my project) ".config.json" but effectively not installed, something like "npm install thatPackage" occur under the hood.
It's just that operation that i want to prevent WITHOUT effectively touching the db.
Another question pops up now while i'm writing: in the standard nodered deploy, an npm uninstall act also on this file to remove references to nodes?