Node.js Compile Version Mis-Matches?

A Former User

I have already tried it but sometimes … it remakes the queue with the other modules and crashes … that’s why I abandoned this method. otherwise on principle i agree with you :)

after … like i say : “If it want to works like this … let’s go on !”

A Former User

I think MM needs to escape from the dependency of Electron. (Frankly, it is needed only for fullscreen kiosk front, not using any advanced benefits of Electron itself)
or at least modules need to use worker-threading or spawning child process which would be independent from Electron process environment to work with node’s native-modules.

sdetweil

@Sean yeh… could have used my prior startup script to test it out with chrome… start serveronly and use chrome to access

A Former User

@sdetweil
I had used my owns for the same.
Currently, standalone MM executes server(backend) js inside of Electron. That makes the things complex.
It would have been better to execute server outside of MM then launch front Electron for a smooth fullscreen kiosk mode.

Or progressively using Electron’s features might have been better also. Electron can support more advanced features like accessing system resources directly.

Anyway, current structure is somewhat ambiguous. I was frightened.

sdetweil

@Sean yeh, just get my run-start.sh scripts from my repo (added to base in 2.10, yanked out in 2.11)

https://github.com/sdetweil/MagicMirror_scripts
change the start to launch run-start.sh

then can add a config parm to config.js

serverOnly:‘local’,

will do split mode locally serverOnly+ chrome

pillbug22

I thought I’d already done an Electron-rebuild install from the previous troubleshooting listed, but of course I wanted to do it again to verify:

$ cd MagicMirror
$ cd modules
$ cd MMM-MP3Player
$ npm install electron-rebuild
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN MMM-MP3Player@1.0.0 No repository field.

+ electron-rebuild@1.11.0
updated 1 package and audited 204 packages in 17.328s

1 package is looking for funding
  run `npm fund` for details

found 0 vulnerabilities

$ node_modules/.bin/electron-rebuild
✔ Rebuild Complete

then go back up some folders and run:

$ npm run start

…aaaaaand, it opens as expected. Absolutely no clue what was different this time around. I went back and looked, and looks like I did already do this as per previous troubleshooting I found, but there must have been something different about how you guys suggested I install and run the electron-rebuild than what I did previously.

Another one of those “just needed a different set of eyes on it” issues, but glad you all were here to be the ones to look :-) Thank you much!

Now to go play around some more and see if I can actually get it to work correctly…but at least the mirror is back up and running

A Former User

@pillbug22 : happy to help you :)