Request for npm packages so I can migrate my n8n instance
I currently have n8n running on a separate server and would like to consolidate it to Cloudron especially since it's calling other apps on Cloudron (like Miniflux). However, there are a few packages that I currently use that I don't see in the currently repository that would prohibit me from migrating. Below is a list of packages (sorry it's long) of packages that aren't on Cloudron and I either currently use them, working on developing them, or plan to use them in the near future. I noticed "@azure" was listed as a package, but I wanted to make sure that all the azure packages are included.
One thing that I don't know if it would ever be possible on Cloudron is if it will be able to do browser automation via n8n. That's something I really want to do so I can really get away from third party services and automate a BUNCH of stuff.
Anyway, here's the list... let me know your thoughts:
Currently In Development:
Planning To Do Soon: Browser Automation
unlighthouse (or auto-lighthouse)
webdriverio (may not be necessary)
@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.
@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.