Read the statement by Michael Teeuw here.
MMM-Pir upgrade problem
-
I recently attempted to perform an update for the MMM-Pir module and it didn’t seem to work. I attempted the ‘npm run rebuild’ command, and now I am getting the following error message:
FATAL: 1 needed library not loaded
Here is what I am seeing when I attempt the rebuild:pi@raspberrypi:~/MagicMirror/modules/MMM-Pir $ npm run rebuild
MMM-Pir@1.0.1 rebuild
installer/rebuild.shWelcome to MMM-Pir rebuild script
This script will erase current build and reinstall it
Do you want to continue ? [Y/n]
Your choice: YDeleting: package-lock.json node_modules
Done.Upgrading EXT-Pir…
HEAD is now at 97f6cc8 update for vulnerabilities security // add node v16.14.0 min requirement
hint: Pulling without specifying how to reconcile divergent branches is
hint: discouraged. You can squelch this message by running one of the following
hint: commands sometime before your next pull:
hint:
hint: git config pull.rebase false # merge (the default strategy)
hint: git config pull.rebase true # rebase
hint: git config pull.ff only # fast-forward only
hint:
hint: You can replace “git config” with “git config --global” to set a default
hint: preference for all repositories. You can also pass --rebase, --no-rebase,
hint: or --ff-only on the command line to override the configured default per
hint: invocation.
Already up to date.
Done.
Reinstalling MMM-Pir…
npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: @npmcli/fs@3.1.0
npm ERR! notsup Not compatible with your version of node/npm: @npmcli/fs@3.1.0
npm ERR! notsup Required: {“node”:“^14.17.0 || ^16.13.0 || >=18.0.0”}
npm ERR! notsup Actual: {“npm”:“8.5.5”,“node”:“v17.9.0”}npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2023-07-11T23_00_51_522Z-debug-0.log
pi@raspberrypi:~/MagicMirror/modules/MMM-Pir $What am I missing, and how can I fix this? Thanks in advance…
-
@Freddy_boy said in MMM-Pir upgrade problem:
add node v16.14.0 min requirement
he updated his module to require node 16.14 minimum
node”:“^14.17.0 || ^16.13.0 || >=18.0.0”}
npm ERR! notsup Actual: {“npm”:“8.5.5”,“node”:“v17.9.0”}and one of the dependencies says it needs
14.7
16.13
or greater than or equal to 18.0u are on 17.9
I would guess upgrade to 18.0 at least
the next release (Oct 1) of mm will move to 18 as 16 is end of life Sept 1.
-
Beautiful. That solved the issue. Thanks for the quick response.