- n8n version: 1.26.0
- Database (default: SQLite):
Running n8n via Docker
when developing custom nodes, is there an option for n8n to watch for changes and restart ? Or a way of reloading the node ?
Having to remember to stop and start the n8n process after every change in a node can be … tedious 
It looks like your topic is missing some important information. Could you provide the following if applicable.
- n8n version:
- Database (default: SQLite):
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app):
- Operating system:
Perhaps @Jon or @marcus can share some tips here? 
anyone have some insight ?
If the node is being created outside of n8n there isn’t a way I can think of. When I make community nodes I tend to make it in the n8n project then copy the node out when I am done as I find it easier.
If doing it that way do you only need to refresh the browser on changes?
That’ll be a life saver. the N-8-N-S-T-A-R-T keys are starting to wear out on my keyboard lol
There is a dev_reload env option that can be set that can be useful if using pnpm dev
I knew there had to be a better way. I’ll check this out tonight, thanks