Read the statement by Michael Teeuw here.
MMM-MoonPhase
-
Hello to all forum. Recently my rasberry’s SD card crashed and I Installed everything from scratch. I have only one problem with MMM-MoonPhse which cannot be installed. I had this one in my previous MM and was working fine. Does anyone know if something happened? Below is the errors I am getting during installation. I am not a programmer so I would be grateful if somebody spot something wrong on my side.
Cloning into 'MMM-MoonPhase'... remote: Enumerating objects: 214, done. remote: Counting objects: 100% (42/42), done. remote: Compressing objects: 100% (33/33), done. remote: Total 214 (delta 15), reused 18 (delta 9), pack-reused 172 Receiving objects: 100% (214/214), 1.07 MiB | 2.76 MiB/s, done. Resolving deltas: 100% (85/85), done. npm ERR! code ERESOLVE npm ERR! ERESOLVE could not resolve npm ERR! npm ERR! While resolving: MMM-MoonPhase@1.0.1 npm ERR! Found: stylelint@14.16.1 npm ERR! node_modules/stylelint npm ERR! peer stylelint@"14.x" from grunt-stylelint@0.18.0 npm ERR! node_modules/grunt-stylelint npm ERR! dev grunt-stylelint@"latest" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! dev stylelint-config-standard@"latest" from the root project npm ERR! npm ERR! Conflicting peer dependency: stylelint@15.2.0 npm ERR! node_modules/stylelint npm ERR! peer stylelint@"^15.0.0" from stylelint-config-standard@30.0.1 npm ERR! node_modules/stylelint-config-standard npm ERR! dev stylelint-config-standard@"latest" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force, or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! See /home/anthony/.npm/eresolve-report.txt for a full report. npm ERR! A complete log of this run can be found in: npm ERR! /home/anthony/.npm/_logs/2023-03-15T16_21_25_597Z-debug-0.log
Thank you in advance.
-
@Anthony not sure if this is related but I see you are cloning into moon phase. That folder shouldn’t exist yet and should be cloning into modules folder instead. I can’t see your commands before that to make sure that’s what you’ve done.
-
@swvalenti git tells u the new folder name where the files will be
-
@Anthony Contrary to the instructions, you do not need to run
npm install
for this module. This would only install packages for development, these are not necessary for you to use the module. -
@KristjanESPERANTO , @sdetweil , @swvalenti Thank you for your replies. As I remember I run
npm install
at the first time and I had no problems. I will try it without this command as well but I do not think this is the problem. -
Just tried it on mine no issues and no npm install
-
@swvalenti you were right. it worked just fine without npm command. Thank you.