how to update my MM

sdetweil

@rikko14 npm init -y

what is going on…

the instructions say

cd modulename (where modulename is the module having the error)

if the module does NOT provide a file called package.json, then do

npm init -y

why are you doing this in the users home folder?

RIKKO14

so i have to do first : cd ~/MagicMirror/ and after npm init -y that’s right ?

sdetweil

@mumblebaj said in how to update my MM:

Maybe combine the script and check if exist then update, else frsh install? Would that work?

what? check if what exist?

the problem here is that i looped thru all the installed modules, and found a package.json, which now requires a new
npm install

in the module folder, BUT, the npm install failed cause of the networking problem

one that is finished, I loop thru all the modules and check to see if they use one of the troublesome libraries
and do NOT reference it in package.json…
and if NO package.json, then I create one, and THEN do the npm install of the library

phew, all the same as the instructions i gave in the linked topic.

but there might be ANOTHER library too … that I don’t handle…

sdetweil

@rikko14 it says

to fix this you need to install the library in the module folder

cd ~/MagicMirror/modules

cd modulename (where modulename is the module having the error)

SO, you have to cd ~/MagicMirror/modules/modulename

same as every other time you were told to cd modulename

RIKKO14

I’m lost …
here are all the modules I have installed.

I have to do: cd ~ / MagicMirror / modules / modulename for each module and then npm init -y ?
and post here all the results of npm init -y ?

I have already had this Electron problem several times and I do not remember what I had typed as the command line but it was not that

mumblebaj

@sdetweil said in how to update my MM:

what? check if what exist?

What I was referring to is for a single script to run, check if MagicMirror exist, check version and upgrade if not on the latest, if not exist then do a fresh install. This way whoever runs your script does not run the wrong one. Just a suggestion.

sdetweil

@rikko14 look in the pm2 logs output

search for Cannot find module

sorry for the dual use of the word module. NPM calls the library a module and MagicMirror calls its app a module…

after that string, there will be a name in quotes ‘request’ or ‘valid-url’, or maybe something else

on one of the next lines will be a file path

MagicMirror/modules/??? some MagicMirror module name

THAT is the MagicMirror module which is missing the library found in the 'Cannot find module ’ message above

So, navigate to that MagicMirror module folder

cd ~/MagicMirror/modules/modulename

and then look for the package.json file

ls package.json

if you get ‘No such file or directory’ in response to the ls command, then create the file by doing

npm init -y

next step,

npm install ???
where ??? is the name of the missing library in the message ’ Cannot find module ’

done for this library for this MM module

sdetweil

@mumblebaj oh… no… don’t want to get into that

they are two distinct functions… users have to learn sometime

mumblebaj

@sdetweil :-) I understand. But it would make your life easier with running the wrong script, messing up their install and you having to go through a 100 different things for them to do to get it fixed… :-)

sdetweil

@mumblebaj they can’t mess up their install …

install aborted as already present

upgrade won’t change anything unless you ask for it.
and it won’t try to upgrade to the same version, unless you report it and I tell you how to get around it.
(I am constantly finding things that users don’t understand, and trying to make life easier as best I can)

this particular problem is unrelated to the scripts…

it was caused by a networking problem I can’t fix.
and I don’t know if all this will work .