Read the statement by Michael Teeuw here.
update
-
Good morning
I can’t update MMM-MeteoFrance.fr
see error message.
Sincerely.patrick@raspberrypi:~ $ cd ~/MagicMirror/modules/MMM-MeteoFrance
patrick@raspberrypi:~/MagicMirror/modules/MMM-MeteoFrance $ git pull
astuce: Tirer sans spécifier comment réconcilier les branches divergentes
astuce: est découragé. Vous pouvez éliminer ce message en lançant une des
astuce: commandes suivantes avant votre prochain tirage :
astuce:
astuce: git config pull.rebase false # fusion (stratégie par défaut)
astuce: git config pull.rebase true # rebasage
astuce: git config pull.ff only # avance rapide seulement
astuce:
astuce: Vous pouvez remplacer “git config” par “git config --global” pour que
astuce: ce soit l’option par défaut pour tous les dépôts. Vous pouvez aussi
astuce: passer --rebase, --no-rebase ou --ff-only sur la ligne de commande pour
astuce: remplacer à l’invocation la valeur par défaut configurée.
Mise à jour 06e94f9…047a887
Fast-forward
MMM-MeteoFrance.js | 89 +±-
eslint.config.js | 22 ±
installer/postinstall.sh | 3 +
package-lock.json | 1040 +++++++++++++++++++±-------------------------
package.json | 16 ±
5 files changed, 479 insertions(+), 691 deletions(-)
patrick@raspberrypi:~/MagicMirror/modules/MMM-MeteoFrance $ npm install
npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: @eslint/config-array@0.18.0
npm ERR! notsup Not compatible with your version of node/npm: @eslint/config-array@0.18.0
npm ERR! notsup Required: {“node”:“^18.18.0 || ^20.9.0 || >=21.1.0”}
npm ERR! notsup Actual: {“npm”:“10.1.0”,“node”:“v20.8.0”}npm ERR! A complete log of this run can be found in: /home/patrick/.npm/_logs/2024-11-13T07_25_12_585Z-debug-0.log
patrick@raspberrypi:~/MagicMirror/modules/MMM-MeteoFrance $ -
so I think the message is considered resolved, thank you kindly
-
npm ERR! notsup Required: {“node”:“^18.18.0 || ^20.9.0 || >=21.1.0”}
npm ERR! notsup Actual: {“npm”:“10.1.0”,“node”:“v20.8.0”}yes, the module says it needs 20.9.0
and you are on 20.8.0
so you need to upgrade node on your machinecan you try these commands, to see if you have either of these tools installed, n or nvm
which n which nvm
if either returns something , it will be the path to the executable.
-
@sdetweil THANKS
I just tried both commands, none of them work, nothing happens, however, the update must have worked because no more messages and the module works correctly, thank you
Sincerely -
I just tried both commands, none of them work, nothing happens, however,
ok, these commands produce output ONLY if they FIND the named command,
its just test of the PATHso you don’t have either installed… ok
the npm install of the updated package SHOULD have failed…
BUT the new code is present, (from the git pull)and if you did NOT need to npm install for the update, then all would be ok…
-
so I think the message is considered resolved, thank you kindly
-
@pat59 I think you are lucky
-
-
HELLO I ALSO THINK THANK YOU AGAIN