Read the statement by Michael Teeuw here.
MMM-NewPIR v3
-
can i add an exception module to not hide, while hiding all others?
-
What is this module made for…RPI3 or RPI4?
-
@cowboysdude I don’t understand the question?
it supports all the different screen dimming approaches
-
@sdetweil Thanks Sam.
-
Hi guys,
After updating my MagicMirror to the latest version, this modules does not work. I tried reinstalling but its giving an error that i do not understand. Could someone help please? I have attached the logs, not sure if they will help.
at Module._compile (internal/modules/cjs/loader.js:778:30)
npm WARN notsup Unsupported engine for electron-rebuild@3.2.3: wanted: {“node”:“>=12.13.0”} (current: {“node”:“10.24.0”,“npm”:“6.13.6”})
npm WARN notsup Not compatible with your version of node/npm: electron-rebuild@3.2.3
npm WARN notsup Unsupported engine for @malept/cross-spawn-promise@2.0.0: wanted: {“node”:“>= 12.13.0”} (current: {“node”:“10.24.0”,“npm”:“6.13.6”})
npm WARN notsup Not compatible with your version of node/npm: @malept/cross-spawn-promise@2.0.0
npm WARN notsup Unsupported engine for fs-extra@10.0.0: wanted: {“node”:“>=12”} (current: {“node”:“10.24.0”,“npm”:“6.13.6”})
npm WARN notsup Not compatible with your version of node/npm: fs-extra@10.0.0
npm WARN notsup Unsupported engine for yargs@17.2.1: wanted: {“node”:“>=12”} (current: {“node”:“10.24.0”,“npm”:“6.13.6”})
npm WARN notsup Not compatible with your version of node/npm: yargs@17.2.1npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @bugsounet/pir@1.0.6 postinstall:electron-rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @bugsounet/pir@1.0.6 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above. -
@philmavedzenge said in MMM-NewPIR v3:
npm WARN notsup Unsupported engine for yargs@17.2.1: wanted: {“node”:“>=12”} (current: {“node”:“10.24.0”,“npm”:“6.13.6”})
You need to update npm and node
-
@djboob66 said in MMM-NewPIR v3:
@philmavedzenge said in MMM-NewPIR v3:
npm WARN notsup Unsupported engine for yargs@17.2.1: wanted: {“node”:“>=12”} (current: {“node”:“10.24.0”,“npm”:“6.13.6”})
You need to update npm and node
Thanks for the response. How do I do that? Which folder should I update it in?
-
@philmavedzenge in your home directory execute following two commands:
sudo npm install -g n sudo n latest
This installs the latest node version
Edit: added sudo
-
Ok you need to find a working node and npm for all module if you have Bugs Google Aisstant v3 then it is best to check the module first GA v3 needs,
Node: v12.x.x upto v14.x.x
npm: = v6.14.15 (some trouble with v7.x)
I suggest trying.
Do in this order.sudo npm cache clean -f sudo npm install -g n sudo n 14.0
now check npm with
npm -v
If 6.14.15 do nothing more but over 7.x use belowsudo npm install -g npm@6.14.15
-
@djboob66 you’re right…I forgot that there might be potential issues with the latest version. Thanks for the correction!
@philmavedzenge : Generally I’d recommend to use @sdetweil update script when updating to a new MM version. (see here) As you already updated to 2.17.1, use this command with
force
at he end instead ofapply
bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" force
Sam‘s script checks, if the correct node and npm versions are installed and updates them accorgingly if necessary.