Read the statement by Michael Teeuw here.
Updated to 2.17 but MM not launching
-
@sdetweil Hi…
git pull & npm installnode -v v14.17.3
npm -v 6.14.13 -
@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 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
-
@sdetweil do you think the error came from a module?
-
@stoffbeuteluwe don’t know, but think so
-
@sdetweil thanks …will try to find it
-
@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?
-
@stoffbeuteluwe did u try the recovery steps I provided before, in the module folder
delete a file
delete a folder
npm install -
@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: