Updated to 2.17 but MM not launching

[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

[Stoffbeuteluwe]

@sdetweil do you think the error came from a module?

[sdetweil]

@stoffbeuteluwe don’t know, but think so

[Stoffbeuteluwe]

@sdetweil thanks …will try to find it

[Stoffbeuteluwe]

@sdetweil Sooo:grinning_face_with_big_eyes: after long searching …I know it is the MMM-AlexaControl module but what does the error mean and what can I do?

[sdetweil]

@stoffbeuteluwe did u try the recovery steps I provided before, in the module folder

delete a file
delete a folder
npm install

[Stoffbeuteluwe]

@sdetweil Hi , yes I have done that and done a new install but the same error …but it works fine :man_shrugging_medium_skin_tone:

[sdetweil]

@stoffbeuteluwe ok. I don’t remember seeing that on my setup. will check

[sdetweil]

@stoffbeuteluwe i just reinstalled AC

and see the same error… its a problem in a library used by a library that the module uses.

nothing u can do to fix it…

[Stoffbeuteluwe]

@sdetweil OK thank you very much Sam……but it works fine