Read the statement by Michael Teeuw here.
MMM-Lunartic
-
@Mykle1 D’oh! Can’t believe I missed that too - my kingdom for an actual helpful nodejs debug message with pointers to the offending line. Works great now. Thanks for the response!
-
No, thank you. Just a stupid mistake on my part.
MM has a command that will check your config and point out the errors but that command escapes me. I’ll take a look for it. Otherwise, jshint.com and jslint.com are pretty useful when I remember to actually USE them. :-)
Cheers
-
Found it! Here is the command that will check your config if you get that error at launch. I assume you need to run it in the MagicMirror directory
npm run config:check -
I removed the comma from the config and ran
npm run config:check. The result would be enough to determine the cause.daddle@daddle-Presario-CQ57-Notebook-PC:~/MagicMirror$ npm run config:check > magicmirror@2.1.3 config:check /home/daddle/MagicMirror > node tests/configs/check_config.js Checking file... /home/daddle/MagicMirror/config/config.js Line 30 col 9 Expected '}' to match '{' from line 28 and instead saw 'distance'. Line 30 col 17 Expected '}' to match '{' from line 25 and instead saw ':'. Line 30 col 19 Expected ']' to match '[' from line 24 and instead saw 'miles'. Line 35 col 6 Missing semicolon. Line 35 col 5 Unrecoverable syntax error. (55% scanned). daddle@daddle-Presario-CQ57-Notebook-PC:~/MagicMirror$ -
I’m astonished by the fact that “npm run config:check” seems to be so unknown in the community. It is a VERY important tool in my opinion.
Whenever there is something odd, always run this one first to check if the config is ok.
However, it took me about twenty lookups into the github readme to finally remember it correctly. -
The terrible thing is that this command was exactly what I spent most of the afternoon yesterday looking for, and it’s apparently nowhere in the popular search results for debugging MM. (Git readme? Pffffft. Clearly my brain was not in a “RTactualFM” mood…lesson learned.) I’ll totally be preaching it now. Thanks for the info and demonstration!
-
@lavolp3 said in MMM-Lunartic:
I’m astonished by the fact that “npm run config:check” seems to be so unknown in the community. It is a VERY important tool in my opinion.
Well, it is a relatively new function, introduced in the last update to MM (I think). I had to look for the command because I don’t use it usually. However, I agree that it is a valuable tool
-
@thetalentedfool said in MMM-Lunartic:
it’s apparently nowhere in the popular search results for debugging MM.
I’ll write up a simple tutorial and post it so that it is easier to find using the forum search function.
-
Great idea Mykle1! Thanks in advance for the effort :-)
The function is not that new.
I’m using it for a few months now, I’d guess. -
@lavolp3 said in MMM-Lunartic:
I’m using it for a few months now, I’d guess.
Ok, but it’s not available in MM version 2.1.1 or 2.1.2 (I think) so that would only make it available in the most recent version (2.1.3). I did say relatively new. :-)
