Request for npm packages so I can migrate my n8n instance
-
-
@ajtatum It's on my list. I did have a quick look the other day, but it's not a straightforward fix since it seems n8n does not use NODE_PATH. So, I have to investigate more on how to make this work. Maybe I will open an upstream issue.
-
@girish I have my instance using nvm's path as I have multiple versions of node js required on the server. So n8n has it's own login with it's own nvm path and for the app itself, I have it look at nvm's node. Just letting you know how I have it in case it helps at all.
Thanks,
AJ -
@ajtatum It seems that n8n does not use NODE_PATH atleast. So, I am not sure how one have an updatable instance with custom packages. Can you please share, what you do in your current instance? How do you update n8n after installing custom modules?
-
-
-
@girish To be honest, I'm not exactly sure. My n8n instance is setup so that the packages allowed are in both the environment file and get loaded as environment variables in the .bashrc script (I know it's doubling, but I can't recall which way worked). When there's an update, I just run npm install n8n@version, and then run pm2 restart and, well, it just works.