Keyboard Shortcut for Developer Tools

sdetweil

@ankonaskiff17 the dev window keyboard shortcut is

ctrl-shift-i

ankonaskiff17

@sdetweil I’m baffled. I get a ton of errors, none of which appear to be anything I would even interact with.
I was wrestling with MMM-NewsFeedTicker when I first posted. So I commented out that portion of config.js restart, everything good.
So I tried a different module, MMM-SystemStats, same exact result, installed module in mm/modules like I am supposed to, copied the config portion, pasted in to config.js, restarted MM, black screen. Commented out its portion config file, restarted everything runs.

FWIW I have refortmatted sd card, installed Pi OS, then MM like 3 times, all with the same exact reslt

sdetweil

@ankonaskiff17 search the errors for ‘module not found’

clear the logs with pm2 flush

then do one run, stop and look at the logs…

–lines=100 might not be enough

u can send the output to a file so you can look at it

pm2 logs --lines=200 >somefile.txt

then edit somefile.txt

ankonaskiff17

@sdetweil I’ve seen those but those all are parts that I don’t know how to fix. I get that it is telling me it needs a module but not sure where to get that module then how to subsequently install. I’m capturing the first error at each time stamp as I assume other following errors just downstream effect

Uncommenting SystemStats I get the below:

[ERROR] WARNING! Could not load config file. Starting with default configuration. Error found: Error: Cannot find module 'request'

Recommenting SystemStats, uncommenting NewsFeedTicker I get:

[13.07.2021 15:46.38.418] [ERROR] Error: Cannot find module 'request'

sdetweil

@ankonaskiff17 right, request was remove in 2.16, as documented in the release notes

Bump node-ical to v0.13.0 (now last runtime dependency using deprecated request package is removed).

this is because it was dangerous and not going to be updated

SO, workaround, is to go to each module folder (reporting the error) and do

npm install request

ankonaskiff17

@sdetweil That was the ticket, Is it just random modules use that request module or is there a common thread among the modules that require(d) use of that module?

Also, is that something module developers have to fix? I was using on my original MM an iFrame module and when I was going to use it this time there was a notice on developers readme.md with about an 80 sized font saying this module broken after that 2.16 update. I’ll leave it at that.

Do you all post issues and work-arounds in like this github repository?

I already know of a module that was doing same yesterday

sdetweil

@ankonaskiff17 i don’t post anything… cause no one reads them

this is a common old module lack of experience sloppiness…

they didn’t document in their package.json files that they used libraries ‘cause it just worked’

and now doesn’t.

for every library they use in their node_helper
they should do

npm install library_name --save

then when YOU get the module and do npm install IT will figure out if that module is ALREADY installed or not and if not install it…

ankonaskiff17

@sdetweil Thank You. I do appreciate the help.
I’m going to post another question but it’s kinda-sorta a CSS and code editor question so will post there.