Default Weather module still not displaying

Blackeye

@Jarhead96097 Could be the comma after “true” on the last line of config … not necessary, and causes an error when I run a :check

sdetweil

@Jarhead96097

I added a command above to restore the original weather.js from the git repo

Jarhead96097

@sdetweil I added “npm audit fix” as there was 1 high severity vulnerability found. It didn’t solve the vulnerability (didn’t try “npm audit fix --force”), and I’m getting the same error.

Jarhead96097

@sdetweil Oh, okay. Let me try that updated string of commands…

sdetweil

@Jarhead96097 please never do audit… causes more problems than it fixes

mumblebaj

@Jarhead96097 Rule of thumb is to never run npm audit fix.

sdetweil

@mumblebaj and we have found npm install parms to turn off the warning coming in next release, and already in my scripts.

mumblebaj

@sdetweil That’s great

Jarhead96097

@sdetweil Good to know…that may be the root cause of all of this. After rebuilding my MM on 2.20.0, I did the npm audit fix. If we can’t get to a resolution in the next few minutes, I’ll chalk this up to a learning experience and do another rebuild.

OldSunGuy

May I ask how you are using

classes: "daytime_scheduler"

Are there two instances of

daytime_scheduler

I use

classes: “currentweather”

type: “current”

and

classes: “weatherforcast”

type: “forecast”

to replace the deprecated modules.