Read the statement by Michael Teeuw here.
How to Troubleshoot
-
@Lexingtonian Thank you for that tip with
npm run config:check. Should be in the dev docs… -
-
While trying to debug modules, I’ve been given quite mixed feedback regarding what to use to print messages to console, on either local system or in remote browser DevTools.
So far, I have found the only reliable way that always seem to print something in the browser, is using
console.error(). The others have varied. I’m on MMv2.2.2 (master). -
I was pulling my hair out trying to figure out why my modules weren’t loading. The npm run config:check tip is a total lifesaver - found a missing comma in two seconds.
-
@BiaGen the latest 2 releases run config check as part of startup, and fail if there is an error like that
I always recommend using manual start whenever changing config, for this very purpose
Stop pm2 mgmt if managing the app
Then
cd ~/MagicMirror
npm startIf any problems they are right there
Once good, ctrl-q MagicMirror
And then use pm2 to launch
