Update from 2.15 to 2.16

sdetweil

@andyyy sudo npm install -g npm@6.14.3

you will then have to cleanup from 7

cd ~/MagicMirror
rm -rf node_modules
npm install

u may have to do the same in any module folder with a package.json file

andyyy

@sdetweil

made it with npm install -g npm@6.14.14.

I still have issues with the default wheater module. The old “currentweather” module works but new default “weather” module just says “loading”.

sdetweil

@andyyy I would look in the window where u start mm

npm start or pm2

if pm2, the pm2 logs --lines=100

for any messages

loading is the default output til data arrives.
so it didn’t get the content from the api

is that forecast u are waiting for?
there is a timing issue, workaround with setting
(look it up for exact spelling)
initialLoadDelay:100

andyyy

@sdetweil

I screwed up my MM entirely. pm2 crashed randomly for an unkown reason.

When did “npm intall” on all modules after the update to 2.16, mostly npm complaints about some vulnerabilites. So I did “npm audit fix” on all them all. Maybe some dependencies broke rather than being fixed.

Another thing; npm complaint that 2.16 is uncompatible with node 10.x and npm version. So upgraded both to the latest one.

Mostly like all that ruined my MM.

Thus, I loaded back last working backup and just did “npm install” on all modules. Npm is still complaints about the node version, but all module run except MMM-MyCalender which seems to be uncompatible with 2.16.

sdetweil

@andyyy don’t run audit fix… ever… makes more of a mess than it fixes

what is the problem with MyCalendar?

karsten13

@sdetweil no package.json and requesting valid-url …

sdetweil

@karsten13 fun times!

sdetweil

@andyyy valid-url was removed in 2.16 as the library it uses was also removed…
but you can add it back for this module

cd ~/MagicMirror/modules/MMM-MyCalendar
npm init

hit enter thru the prompts

npm install valid-url --save

the author should fix the module, but many authors are no longer maintaining their modules

andyyy

@sdetweil

Thx, after fixing this the next lib is missing. I just give up using that module.

I have a vision for the future MM development. All modules should run in a separate container/sandbox or capasulated/isolated somehow. So when they fail for whatever reason, the MM stays alive and reporting a specific error message.

Don’t get me wrong I highly appreciate the work/effort of michmich and his team.

sdetweil

@andyyy i think that MM should fail when a module fails and make it easier to find