@geekhouri yep, 
we’ve been cleaning up the mm core tubing for 2 years now. this module was using one of the libraries we supplied, but didn’t declare it.
if you had used my upgrade script I would have handled this problem for you
see
https://forum.magicmirror.builders/topic/15778/fix-for-black-screen-in-2-16-and-later
in the module folder do
npm install request
@geekhouri nothing we/you can do. a library uses a library which uses a library which was upgraded. but we can’t make anyone upgrade, and mm is a special env. it’s not a public website doing banking. it’s just showing some info pulled into. your house .
so, all you can go is ignore it. oh, and don’t do audit fix. it forces a bunch of changes, some of which break existing code, with no fix available.
@1a2a3a means it was not accidental. it’s not trivial to maintain visual fidelity across multiple rendering platforms and aspect ratio changes.
the module author(s) chose not to attempt that
@Klinge fall back to the prior calendar parser
cd ~/MagicMirror
npm install node-ical@0.16.1
restart mm
your config looks ok
@carefreepineappl use the secret url.
there are no other Google providers
@J2FK see the doc on my fork, there is no code change
https://github.com/sdetweil/MMM-pages#using-the-module
see the ‘alternative approach’
makes all these issues go away
@fischi87 that message should really be a warning, as it causes no trouble, and the code handles the issue
@DDE12 those are warnings we can’t suppress… nothing we can do… problem is not in MM code…
when the mm screen goes black again , open the developers window
ctrl-shift-i on the MM screen keyboard
then select the console tab, and scroll up to any errors (usually red text )
cannot do this remotely has to be on the screen where the problem occurred