Node.js Compile Version Mis-Matches?

[A Former User]

@sdetweil : are you sure of this ?
install and execute electron rebuild inside main MM core !?

[sdetweil]

@Bugsounet sure, it will find what it needs to rebuild

[A Former User]

and scan … ALL modules …

[sdetweil]

@Bugsounet so, it will do it quickly… go get some coffee… everything not done in 2 seconds! lol

[A Former User]

lol

so the better thing is that :
install electron rebuild inside the module desired (there MMM-MP3Player)

cd ~/MagicMirror/modules/MMM-MP3Player
npm install electron-rebuild

and execute it

./node_modules/.bin/electron-rebuild

[sdetweil]

@Bugsounet better not to install it 12 times , just one in MM, then maybe use in module folder…

too many modules need rebuild

[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.