Read the statement by Michael Teeuw here.
Complete Walkthrough - Install MagicMirror on a PC - Windows 7/10
-
this is because npm 7.14 is trying to launch from the MagicMirror folder instead of the module folder…
-
@sdetweil can i install npm v6 ?
-
@airart yes,
npm install -g npm@6.14.0
after this completes
cd MagicMirror rd /s/q node_modules npm install
-
@sdetweil in which folder it should be installed
-
@airart -g means global
-
@sdetweil it works ! I am so moved, evidently that was the problem.
Does CMD remain active how do I leave the MM? fn + f11 reduces to window
I also noticed some warnings -
@airart ctrl-c in ther terminal window will stop the active program
ignore warnings
-
Thanks for the tutorial, i’m running magicmirror on a surface pro 4,
The installation worked perfectly but when i tried to run npm start it throw an error “> DISPLAY=”${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js"
To bypass the error i edited the package.json by removing the DISPLAY="${DISPLAY:=:0} at the begining, tried npm start and it worked.
I’m not sure for what is that display option.
-
@matefits71 on Linux, the xwindows graphical system writes to a numbered ‘display’ , and there can be multiple.
windows doesn’t have that. which is why I’ve written to remove that part, and also run the manual npm install in vendors and go ta folders
-
$ npm start
magicmirror@2.16.0 start C:\Users\Tecsis\MagicMirror
DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js“DISPLAY” no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! magicmirror@2.16.0 start:DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the magicmirror@2.16.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Tecsis\AppData\Roaming\npm-cache_logs\2021-09-02T01_57_52_304Z-debug.log