@bolish
OK that didn’t help.
MMM-Logging at least gave us the file putting the error out but not file from which it originated.
But isn’t Linux a beautiful wild monsterous creature?
Try this command
find . -maxdepth 2 -exec grep -nwl Promise 2>/dev/null {} +
in the MagicMirror directory.
“find” looks for all files in the 3rd party module directories (all files with depth of 2 directories maximum, we don’t want to have all the numerous node module files included), then it executes (“-exec”) a grep function searching the files for the “Promise” function.
“2>/dev/null” is there to put all error output (there’s a lot) away from the standard output
This will give you all 3rd party module files including the promise function. Then we can limit it to a few modules.
With these you can do the “deactivate and look for errors” workflow and find out the one responsible