Updated to 2.17 but MM not launching

OberfragGER

@sdetweil said in Updated to 2.17 but MM not launching:

``|

Thanks a lot. That did the job for me!

Stoffbeuteluwe

Hi Sam, i have to do this for 11 modules :grinning_face_with_big_eyes: …but that’s not the problem it takes a little time…but do I have to do all this again on every next MM Update?:dizzy_face:

Greeting from Germany

Stoffbeuteluwe

The Mirror works but there are some errors…

[14.10.2021 21:09.11.218] [ERROR] (node:48778) Warning: Accessing non-existent property 'cat' of module exports inside circular dependency
(Use `Electron --trace-warnings ...` to show where the warning was created)
[14.10.2021 21:09.11.218] [ERROR] (node:48778) Warning: Accessing non-existent property 'cd' of module exports inside circular dependency
[14.10.2021 21:09.11.218] [ERROR] (node:48778) Warning: Accessing non-existent property 'chmod' of module exports inside circular dependency
[14.10.2021 21:09.11.218] [ERROR] (node:48778) Warning: Accessing non-existent property 'cp' of module exports inside circular dependency
[14.10.2021 21:09.11.218] [ERROR] (node:48778) Warning: Accessing non-existent property 'dirs' of module exports inside circular dependency
[14.10.2021 21:09.11.218] [ERROR] (node:48778) Warning: Accessing non-existent property 'pushd' of module exports inside circular dependency
[14.10.2021 21:09.11.218] [ERROR] (node:48778) Warning: Accessing non-existent property 'popd' of module exports inside circular dependency
[14.10.2021 21:09.11.218] [ERROR] (node:48778) Warning: Accessing non-existent property 'echo' of module exports inside circular dependency
[14.10.2021 21:09.11.219] [ERROR] (node:48778) Warning: Accessing non-existent property 'tempdir' of module exports inside circular dependency
[14.10.2021 21:09.11.219] [ERROR] (node:48778) Warning: Accessing non-existent property 'pwd' of module exports inside circular dependency
[14.10.2021 21:09.11.219] [ERROR] (node:48778) Warning: Accessing non-existent property 'exec' of module exports inside circular dependency
[14.10.2021 21:09.11.219] [ERROR] (node:48778) Warning: Accessing non-existent property 'ls' of module exports inside circular dependency
[14.10.2021 21:09.11.219] [ERROR] (node:48778) Warning: Accessing non-existent property 'find' of module exports inside circular dependency
[14.10.2021 21:09.11.219] [ERROR] (node:48778) Warning: Accessing non-existent property 'grep' of module exports inside circular dependency
[14.10.2021 21:09.11.219] [ERROR] (node:48778) Warning: Accessing non-existent property 'head' of module exports inside circular dependency
[14.10.2021 21:09.11.219] [ERROR] (node:48778) Warning: Accessing non-existent property 'ln' of module exports inside circular dependency
[14.10.2021 21:09.11.219] [ERROR] (node:48778) Warning: Accessing non-existent property 'mkdir' of module exports inside circular dependency
[14.10.2021 21:09.11.219] [ERROR] (node:48778) Warning: Accessing non-existent property 'rm' of module exports inside circular dependency
[14.10.2021 21:09.11.219] [ERROR] (node:48778) Warning: Accessing non-existent property 'mv' of module exports inside circular dependency
[14.10.2021 21:09.11.219] [ERROR] (node:48778) Warning: Accessing non-existent property 'sed' of module exports inside circular dependency
[14.10.2021 21:09.11.219] [ERROR] (node:48778) Warning: Accessing non-existent property 'set' of module exports inside circular dependency
[14.10.2021 21:09.11.219] [ERROR] (node:48778) Warning: Accessing non-existent property 'sort' of module exports inside circular dependency
[14.10.2021 21:09.11.219] [ERROR] (node:48778) Warning: Accessing non-existent property 'tail' of module exports inside circular dependency
[14.10.2021 21:09.11.219] [ERROR] (node:48778) Warning: Accessing non-existent property 'test' of module exports inside circular dependency
[14.10.2021 21:09.11.219] [ERROR] (node:48778) Warning: Accessing non-existent property 'to' of module exports inside circular dependency
[14.10.2021 21:09.11.219] [ERROR] (node:48778) Warning: Accessing non-existent property 'toEnd' of module exports inside circular dependency
[14.10.2021 21:09.11.219] [ERROR] (node:48778) Warning: Accessing non-existent property 'touch' of module exports inside circular dependency
[14.10.2021 21:09.11.219] [ERROR] (node:48778) Warning: Accessing non-existent property 'uniq' of module exports inside circular dependency
[14.10.2021 21:09.11.219] [ERROR] (node:48778) Warning: Accessing non-existent property 'which' of module exports inside circular dependency

sdetweil

@stoffbeuteluwe said in Updated to 2.17 but MM not launching:

…but do I have to do all this again on every next MM Update

if you do the

npm init

in the module folder before npm install request (or whatever is missing)
then that library will be loaded in the module node_modules list

if NOT, then it looks for the 1st node_modules folder up the directory tree , finds one under MagicMirror and installs the module there

BUT…

on the next update, npm will check and see that this library was not required by MM, and so delete it, (security, so someone can’t sneak libraries into the installed folder)…

so… answer to your question is ‘maybe’…

sdetweil

@stoffbeuteluwe said in Updated to 2.17 but MM not launching:

The Mirror works but there are some errors…

how did u do the upgrade?

can u tell me

node -v
npm -v

output?

this version of electron needs node 14. my script does NOT upgrade node

Stoffbeuteluwe

@sdetweil when I’m home from work I will tell you….thanks in advance

Stoffbeuteluwe

@sdetweil Hi…
git pull & npm install

node -v v14.17.3
npm -v 6.14.13

sdetweil

@stoffbeuteluwe ok, thx… did u use my upgrade script?

if not, I would go thru every module (not defaults) and look for package.json

if present, in the module folder I would

rm package-lock.json
rm -rf node_modules
npm install

to reload the dependencies based on the new MM.
(this is what my upgrade script does)

after that, I would disable one module at a time to find the culprit…

Stoffbeuteluwe

@sdetweil said in Updated to 2.17 but MM not launching:

npm install

Ok thank you Sam i will try…

sdetweil

@stoffbeuteluwe u could use my upgrade script with force

to accomplish the same thing

I would disable modules to find it first, and then check after redoing npm install