Deploying community nodes to n8n without npm publish?

Questions
,
1

Describe the problem/error/question

In order to update a community node, you have to publish a new version through NPM. Then you have to open the n8n instance and update the node manually through the settings page.

This slows down the development/testing cycle significantly, and forces maintainers to publish many versions while developing/debugging.

Has anyone found a simpler solution? A github action or something along those lines to deploy the community node directly to your instance and overwrite the current definition with the “unpublished” version?

2

up.
I want this info too

3

@pedrozb
I encourage you to create a feature request for this.

4

Hi there, our docs contains a guide on how to test your node locally without needing to publish it every time

But also we recently released our CLI - n8n-node which simplifies the node development a lot, it also has an ability to run your node in dev mode with hot reloading and we encourage more node authors to try it out

Hope this helps!

5

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