MMM-ImagesPhotos issue

sdetweil

@Nneuland see https://forum.magicmirror.builders/topic/15778/fix-for-black-screen-in-2-16-and-later

Nneuland

This might be over my head…

pi@raspberrypi:~/MagicMirror/modules/MMM-ImagesPhotos $ npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: magicmirror-images-photos@0.1.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.7.0
npm ERR! node_modules/stylelint
npm ERR! peer stylelint@“^15.5.0” from stylelint-config-standard@33.0.0
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/pi/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2023-06-13T18_03_53_057Z-debug-0.log

sdetweil

@Nneuland ok, fun stuff…

the module is so old that the development dependencies no longer exist…

so

edit the package.json

and change this

  "devDependencies": {

to this.

  "devDependencies1": {

the rerun npm install

another stupid thing, npm gives you the option to NOT install the dev stuff. --omit=dev, BUT it still checks them and fails if they don’t work…

so, we have to force them to not exist…

Nneuland

@sdetweil
thanks Sam. after adjusting the devDependencies in package.json then running npm install seemed to correct the install.

I have auto start mirror enabled when making adjustments to config file. However after adding the config info for this module, the mirror wont start. maybe too old of a module…any suggestions on a better image viewer module?

sdetweil

@Nneuland did u fix the missing library problem??? which is why MM doesn’t start???

Nneuland

@sdetweil

i have not yet. I’ll need to research how to do that properly…

sdetweil

@Nneuland see the link I posted on what to do. no research needed
https://forum.magicmirror.builders/topic/17845/mmm-imagesphotos-issue/2?_=1686706297079

Nneuland

@sdetweil

Thank you Sam!!

sdetweil

@Nneuland are you back up and running?

Nneuland

@sdetweil
I’m gonna give it a go later tonight

Nneuland

@sdetweil
After following your basic instructions I’m still having the issue.

To clarify, after adding the modules config information, the mirror wont start up… removing the config information and saving auto starts the mirror.

sdetweil

@Nneuland correct, did you add the missing library request??

the link says,

read the messages output by MM at startup (which you showed above)
find the not found message, which has the library name in it

use the library name in an

npm install  library_name_here

command while the current folder is the module folder

I am trying to teach you how to resolve this on your own next time… vs just giving u the answer, and having to do that over and over

Nneuland

@sdetweil
Got it! Solved!
Sam, I can’t thank you enough for your time and patience. I appreciate all of your help. Over the years even!
I dont mean to be an annoyance. I find these issues daunting and beyond understanding at times.