you can use --omit=optional
as param for npm install
, I use this for my amd64
images because they are run to 99,9% with npm run server
so electron is not needed
Read the statement by Michael Teeuw here.
Posts made by karsten13
-
RE: electron-rebuild problems with MagicMirror 2.22.0
-
RE: electron-rebuild problems with MagicMirror 2.22.0
@wishmaster270 said in electron-rebuild problems with MagicMirror 2.22.0:
Edit: Do not misunderstand me. In my opinion the best way to solve the electron-rebuild problems of a lot of modules would be to put “@electron/rebuild” as a dependency to “package.json” of MagicMirror.
I don’t have a final opinion on that yet, but if so, we should put it under
optionalDependencies
aselectron
-
RE: electron-rebuild problems with MagicMirror 2.22.0
@wishmaster270 said in electron-rebuild problems with MagicMirror 2.22.0:
@karsten13
They are stored in thenode_modules
folder of the module which should be persistentthats good, so the construction with installing
electron-rebuild
in mm folder has no side effects and works also in a docker setup. -
RE: electron-rebuild problems with MagicMirror 2.22.0
o.k., but where are the compile results stored?
-
RE: electron-rebuild problems with MagicMirror 2.22.0
@wishmaster270 said in electron-rebuild problems with MagicMirror 2.22.0:
and the postinstall script will work as excepted.
yes, will work, but all the changes in the
node_modules
folder of mm are gone with the next restart of the container … -
RE: electron-rebuild problems with MagicMirror 2.22.0
@wishmaster270 said in electron-rebuild problems with MagicMirror 2.22.0:
So the right way is to install electron-rebuild in the same project as electron and call it from there.
installing module stuff in the
node_modules
folder of mm is a hack and will not work out of the box with a docker setup because this folder is only in the container (you have to map it on the host to get changes there persistent)It might be worth to think about adding it as a dependency in the main project.
in this case may the best solution
-
RE: electron-rebuild problems with MagicMirror 2.22.0
@sdetweil said in electron-rebuild problems with MagicMirror 2.22.0:
his was x86_64… (edit: i see his is amd64, oops, tldr;l!)…
I will see if I can get a vm on my new amd64 chromebook… had it til I powered off…@sdetweil said in electron-rebuild problems with MagicMirror 2.22.0:
so not 32 bit.
he wrote 32 bit
x86_64=amd64
: No Raspian OS
arm32v7=arm=aarch32
: Raspian OS 32-bit
arm64v8=arm64=aarch64
: Raspian OS 64-bit -
RE: electron-rebuild problems with MagicMirror 2.22.0
@sdetweil said in electron-rebuild problems with MagicMirror 2.22.0:
his was x86_64…
he wrote “I use a fully patched Raspberry OS Bullseye 32Bit.” so I think this is
arm32v7
but I built on buster and bullseye on pi4 also … MM version 2.22
but his didn’t execute the postinstall scriptstrange
-
RE: electron-rebuild problems with MagicMirror 2.22.0
@sdetweil said in electron-rebuild problems with MagicMirror 2.22.0:
Linux galliumos 4.16.18-galliumos #1 SMP PREEMPT Sun Jun 23 04:14:45 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
thats
x86_64
, notarm32v7
, totally different concerning compiling stuff which is done in electron-rebuild …