Closed erspearson closed 8 years ago
I think what is going on here is that node-red-contrib-rfxcom declares a dependency on 'node-rfxcom', sourced from my Github, but the package.json it pulls in names the package as 'rfxcom'. Hence the one is missing and the other is extraneous. But they are, in fact, different names fro the same package.
I am indeed in the middle of merging the two forks of rfxcom back together, as Kevin McDermott has now added me as a package maintainer. indeed, had the washing machine not expired last weekend it would probably be done by now. Probably within a week I will be able to publish a new version of node-red-contrib-rfxcom that no longer depends on my Github fork.
Kate will help... https://www.youtube.com/watch?v=GZnA4jHuyzs
More of an FYI than an issue. Just moving some flows from Windows to a RPi Bv1 for production on a clean-ish install of Jessie.
Node-RED version: v0.13.4 Node.js version: v0.10.29 Linux 4.1.19+ arm LE
Possibly something to do with the merge of node-rfxcom back into the original being in-flight?
rfxcom is working in nodered. Hence just an FYI.