Read the statement by Michael Teeuw here.
Electron error on install.
-
Thank you so much! this helped me a lot. I do not know why this bug /issue has not been addressed. I used the single-line ¨Automated¨ install and THAT failed first because Node.js was too old, so the one line command does not auto-update Node.js. I figured that out and updated the entire Raspberry pie in the CLI, then re-installed MM from the single line ¨Automated¨ command and then it installed cleanly, but your suggestion here to delete electron, then run npm install then npm start has fixed the last final issues. Thanks again!
-
You’re welcome, mate.
-
@AB_Normal I did not mention in my last post, but to get past the node.js being too old issue, from the TERMINAL window, I typed, sudo apt-get update then, when that was finished I typed sudo apt-get upgrade you first get the files with the update command, then install them with the upgrade command. That will update ALL of the files/librairies/programs, whatever they are called in linux (Iḿ a windows person), INCLUDING node.js. Now if you run the single line automated command in the terminal, then do as Markle1 suggests and delete the ELECTRON folder, then, from the MagicMirror folder in the terminal window run the npm install, then run the npm start command, you MagicMirror will work. OH, Have to do as MArkle1 says and copy and rename the config.js.sample file to config .js also.
-
Replace Markle1 with Mykle1. Sorry , I screwed up your name.
-
@AB_Normal said in Electron error on install.:
Replace Markle1 with Mykle1. Sorry , I screwed up your name.
No worries, mate. I’ve been called worse. :-)
EDIT Click the three dots at the bottom right of your post and choose Edit. Then you can fix whatever you like and no one will be any the wiser. :-)
-
@Mykle1 said in Electron error on install.:
Try deleting the electron folder from this path:
`MagicMirror/node_modules/electronThen run
npm install
in the MagicMirror directory. This should install electron for you.Then run
npm start
in the MagicMirror directoryUnfortunately this didn’t work for me, but I did find a solution. I had to upgrade nodejs manually.
npm cache clean -f npm install -g n n stable