Help with mmm-systemtemperature error messages

[sdetweil]

@thartley did you
npm install
In the module folder after git clone?

[thartley]

@sdetweil - Thank you for the reply. I don’t know if I did or not because it was some time back. Is that a step I can do now without messing things up if it turns out I already did it earlier? Or is there a way to tell if the npm step was done previously before running it now?

[sdetweil]

@thartley you can do it now…

go to the module folder

cd ~/MagicMirror/modules/mmm-systemtemperature
npm install

then restart MagicMirror

from the module readme

In your terminal, go to your MagicMirror's Module folder:

cd ~/MagicMirror/modules
Clone this repository:

git clone https://github.com/MichMich/mmm-systemtemperature.git
Install dependencies:

this leaves out the important step

cd mmm-systemtemperature

then

npm install

[thartley]

@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.

[sdetweil]

@thartley you did NOT need to update npm

[thartley]

@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?

[thartley]

@sdetweil - Hi. Please mark this as resolved since I don’t think I have rights to do that yet.

[sdetweil]

@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

[sdetweil]

@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

[KristjanESPERANTO]

FYI: I’ve created a fork, refactored it and optimized the README. It should be easier to install :-)