so there was one issue in each .js file, I ended up pasting the entire .js repository back in from the GitHub files, that seems it fixed it.

for people having this issue when it black screens, run

cd MagicMirror
npm start dev

that starts up magic mirror with dev options, go to the second tab, there will be files that have errors or security issues, that’s what it was for mine anyway… It’s fixed now, thanks a lot for helping.

I tried it and it did nothing…

oh I see, I’ll try it now

wait so from the site you gave me, if I run

sudo touch /forcefsck; sudo reboot

will that break it?

oh, typo haha, it’s supposed to say main.js, there are no errors in that one either, sorry about that

what do you mean by misn.js, I will have a look at that site, thanks

how would I go about doing that on a pi?

so I had an idea to check through it fast, I copied the loader.js info off of github and paste it into the find (ctrl+f) window, the whole document is highlighted, meaning there are no errors… could it be something else??

Okay, I’ll check through it and correct anything that may be wrong

but in the repository for MagicMirror on github its the same, how do I quickly check for differences instead of having to go through the entire thing and comparing to another file

so I’ve got translator.js open, it says at the top

/* global config, vendor, MM, Module */
/* MagicMirror
 * Module and file loaders.
 * Etc...

should it be

 /* global config, vendor, MM, Module */
 /* MagicMirror*/
 /* Module and file loaders.*/
 /* Etc...

yeah, shame though I’d only just perfected it ahah, so the three errors are

• Uncaught SyntaxError: Invalid or unexpected token (translator.js:1)
• Uncaught SyntaxError: Invalid or unexpected token (loader.js:1
• Uncaught ReferenceError: Translator is not defined (misn.js:452)
  at Object.init (main.js:425)
  at main.js:580
  and then a couple of security warning that I can probably (hopefully) fix.

so I’ve run that and in the top right corner it says 3 errors and 2 warnings, I just don’t understand why it would do this overnight, it was working perfectly last night

So I turned off my mirror last night as per usual and turned it back on this morning to find that the modules aren’t loading, I don’t have a notification saying that I had an error with the config.js folder, the thing autoboots then shows absolutely nothing, I am running the latest version, I ran npm audit which showed 7 low, 1 medium, 1 high, so I ran npm audit fix, now I only have 5 low… but it still isn’t working… Any suggestions where to look or what to potentially do that doesn’t involve starting again??