Latest container and /data bind incompatible

Hello to everyone developing, maintaining or using this fantastic bit of Software.

I am running the latest container with a bind mount for /data, as is the usual an recommended configuration. I noticed the /data directory contains not only settings and flows, but also npm modules.
This is fine for my purpose, but I wonder what happens if I upgrade the container to a new version, and there happens to be a breaking incompatibility? For instance if a newer version of the container has some dependency on a module that cannot be satisfied by the mounted /data?

I am not familiar enough with the Node.JS/npm ecosystem as a whole, maybe this is a non-issue or my understanding of the dependencies is wrong?

The modules that get installed under /data are purely those used by your flows - none of the core modules get installed there. So there should not be any issue around upgrading.

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.