I plan to develop features on a contrib-node, and make a PR (my first with real code!) to the original project on GitHub. What is the best way to do this ? Should I change the package.json to point to my fork during development? Although it won't be published as a npm? Should I reassign git origi…

The easiest way I've found is to firstly stop node-RED and remove the node that you want to work on from your node-RED palette via the cli npm remove <npm-package-name>. Then git clone the contrib node that you want to develop, and follow this guide to add your local 'git' version of the node back …

Thanks. Hadn't thought of removing the original first. I guess I was afraid of difficulties when the flows wouldn't find the node used all over, but of course it won't get started back up before the "imposter" is linked back in the position:)

Yes, thats what I do anyway. I'm pretty sure someone will come along shortly and tell me I've been doing it wrong :grin: :grin: :grin:

In addition it is a good idea to do the development on a branch rather than on master. That way it is easier to identify what you have done.

Yes, I believe they merge PRs to dev branch, so that is my starting point, but I then branch to "feature/[..description..]" and code there.

Thanks both @Paul-Reed and @dceejay . I just think I saw a recipe some time where "npm link" was used extensively. No need then.

Any thoughts on me coding this in VSCode on the mac with the Remote extension so I actually develop this on my raspberry pi ? I have to live test the node with the devices connected only to the pi. Ok ? I should just as easily be able to revert catastrophies there.

Someone who knows more than me told me to fork and then make a new branch in your fork and make the changes in that. Then, when making a pull-request - you do it from your new branch - it keeps things cleaner I was told While developing, I recommend just working on the node files in an alternate i…

[image] bohtho: Any thoughts on me coding this in VSCode on the mac with the Remote extension so I actually develop this on my raspberry pi ? I don't use VSCode but I use Notepad++ in this manner to do the editing so it should work

Thanks for the input from experience! I would like to try to get more familiar with git in the process and be as "pro" as is possible, so I would have thought I could "checkout" the master branch again when pausing development (instead of switching between node-red installations) ? Even from the no…

Developing on fork of node

Developing Nodes

bohtho 8 December 2019 22:18 16

Actually, the branch switching inside the node-RED GUI is related to my flows/project of course, and to make that switching work in this case I would have to have two different package.json files, keep the original node in place on my project's master branch, and also restart all of node-red when switching.... ? Maybe that's a step too far for me, or did I just confuse myself again ?

Topic		Replies	Views
Developing a core node by making a trial contrib node Core Development	8	734	6 November 2019
Node maintenance for dummies Developing Nodes	9	269	28 March 2024
Node-RED Node development in Node-RED? Share Your Nodes	6	629	28 September 2023
Work on a Git branch of Project in the GUI without it going live General	9	894	28 March 2019
Using local node for development & testing Developing Nodes	3	667	5 September 2019

Developing on fork of node

Related topics