Update from 2.15 to 2.16

bdream

@sdetweil I did it but don’t know what to do with these messages :face_with_rolling_eyes:

pi@MagicMirror:~/MagicMirror/modules/MMM-DWD-Pollen $  npm install request --save
npm WARN EBADENGINE Unsupported engine { package: 'magicmirror@2.16.0',
npm WARN EBADENGINE   required: { node: '>=12' },
npm WARN EBADENGINE   current: { node: 'v10.23.1', npm: '7.15.1' } }
npm WARN EBADENGINE Unsupported engine { package: 'eslint-plugin-jsdoc@35.4.0',
npm WARN EBADENGINE   required: { node: '>=12' },
npm WARN EBADENGINE   current: { node: 'v10.23.1', npm: '7.15.1' } }
npm WARN EBADENGINE Unsupported engine { package: 'jsdoc-type-pratt-parser@1.0.4',
npm WARN EBADENGINE   required: { node: '>=12.0.0' },
npm WARN EBADENGINE   current: { node: 'v10.23.1', npm: '7.15.1' } }
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142

added 628 packages, and audited 921 packages in 12m

110 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

andyyy

@sdetweil

I got electron installed again with specifying a version (sudo npm install electron@6.1.12). No idea, why electron disappeared in the first place.

@Fozi

The MMM-MyCalender has indeed an issue with 2.16. causing a black screen. And MMM-Fuel is saying “undefined” for an unknown reason. Both modules are disabled for now.

My MM boots and shows the all other modules again.

With each MM update something crashes, mostly one of the 3rd party modules because one or more dependencies are lost/changed or deleted.

Thanks for your help. Great community!

sdetweil

@andyyy yeh, version 2.1.6 is on electron 11.4.9

sdetweil

@andyyy i see you have npm version 7 installed… causes quite a few problems…

I would fall back to npm 6

andyyy

@sdetweil

How do I revert to npm v6?

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?