Read the statement by Michael Teeuw here.
Help with mmm-systemtemperature error messages
-
@sdetweil - Thank you for the assistance. There are no longer any errors for that module. The system did need to update npm install to a newer version on my system first. After that it the remaining steps went just fine.
-
@thartley you did NOT need to update npm
-
@sdetweil - Maybe I misspoke when I used the word “update”. When I keyed in npm install per your instructions, it came back with several lines, each starting with “npm WARN old lockfile…”.
It took care of something, so maybe it was just doing some sort of cleanup?
-
@sdetweil - Hi. Please mark this as resolved since I don’t think I have rights to do that yet.
-
@thartley you do,
Find the post which best resolves the issue
Hit the 3 dots in the lower right corner
Select
Mark this post as the best answer -
@thartley ok, understood. It upgraded the lock file format,
Useless user message in my opinion, as there is no way to fall back to an older npm which can’t use the new format -
T thartley has marked this topic as solved
-
FYI: I’ve created a fork, refactored it and optimized the README. It should be easier to install :-)
