Read the statement by Michael Teeuw here.
How to properly update modules?
-
Hi, today I have an update on MMM-Wallpaper module too. I updated it using git pull && npm install. A few hours later, I had another update, so I repeated the process. I think it’s not an error. I think it’s the module developer that is making some changes to the code.
Try to check if the response on the terminal is always the same when updating or if they are different. In the case I just told you about, the updates were different.
-
-
@Cliff365 those are from the npm install
you can turn off with --no-audit
so, the git pull worked ok…
if you do it again it should say up to date
-
To be fair, for MMM-Multimonth I did a pair of updates nearly back to back. Screwed up the first one. Update was very minor, you shouldn’t have to re-run NPM Install with it.
As for the security vulnerability - I’m aware… Been trying to re-code around it (It’s moment.js - getting rid of it)
-
@BKeyport u can just turn off the warning, save grief… this is not a general web page that 1000’s will visit…
npm install --no-audit --omit=dev
(updated install and upgrade to do this, stop users from doing dumb audit which screws things up)
-
@sdetweil yeah, well… Like I said, I’m re-writing code anyway. Moment is dead. Might as well bury it.
-
@BKeyport in a few decades maybe…
i’m not rewriting any of mine… -
