ottopaulsen / node-red-contrib-power-saver

A Node-RED node to saver money by turning off when the power is most expensive
Other
71 stars 17 forks source link

Installing v 3.4.4 from palette fails #48

Closed CirruZZ closed 2 years ago

CirruZZ commented 2 years ago

Running Node-red v14.19.0 on Raspbian 10 (buster)

Installing from palette gives the following.

-----------------------------------------------------------
2022-03-19T20:17:30.615Z Install : node-red-contrib-power-saver 3.4.4

2022-03-19T20:17:30.641Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production node-red-contrib-power-saver@3.4.4
2022-03-19T20:17:36.032Z [err] npm
2022-03-19T20:17:36.032Z [err]  WARN floating-vue@2.0.0-beta.8 requires a peer of vue@^3.2.0 but none is installed. You must install peer dependencies yourself.
2022-03-19T20:17:36.063Z [err] npm 
2022-03-19T20:17:36.063Z [err] WARN vue-resize@2.0.0-alpha.1 requires a peer of vue@^3.0.0 but none is installed. You must install peer dependencies yourself.
2022-03-19T20:17:36.064Z [err] 
2022-03-19T20:17:36.066Z [out] + node-red-contrib-power-saver@3.4.4
2022-03-19T20:17:36.066Z [out] updated 1 package in 4.026s
2022-03-19T20:17:36.152Z rc=0

I'm rather novice on Node-red, what do I need to do to fix the dependencies that is mentioned in the logg?

CirruZZ commented 2 years ago

Okey, I'v been trying to get it installed

After that it complained about old lockfile but i don't see that fault anymore.

Now I'm stuck at it saying

-----------------------------------------------------------
2022-03-19T22:42:08.353Z Install : node-red-contrib-power-saver 3.4.4

2022-03-19T22:42:08.259Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production node-red-contrib-power-saver@3.4.4
2022-03-19T22:42:11.332Z [out] 
2022-03-19T22:42:11.332Z [out] up to date in 2s
2022-03-19T22:42:11.354Z rc=0

I can see the folder node-red-contrib-power-saver in $HOME/.node-red

CirruZZ commented 2 years ago

So it seems that node-red-contrib-power-saver was installed and that the issue was somehow in Node-RED. After some restarts it is now showing.

Case Closed!