Read the statement by Michael Teeuw here.
MM won't run, blank screen with cursor showing after updating
-
-
@sdetweil i did npm install in the cd magicmirror folder, as well as the other folders with a package.json, but it is still doing and saying the same thing as before, any ideas?
-
cd MagicMirror/node_modules ls rrule
does anything show?
if not (expect it to be not there)
cd .. npm install rrule
also, edit package.json
u should see this
"rrule": "^2.6.2",
-
@sdetweil i installed rrule in just the normal folder, or the blank cd. where should i edit the package file? like in which folders?
-
@jmartin1009 everything MagicMirror starts in the MagicMirror folder…
in just the normal folder,
what does that mean?
it MUST be in MagicMirror to update the runtime files…the
cd .. (you were in node_modules, so back up one level, now in MagicMirror) npm install rrule
was exact, if you followed my instructions
-
@sdetweil i accidentally installed it in the folder previous to MM, but it still worked, but im installing it in the MM folder right now. Thought you meant the first level cd. Should i remove it in the pi folder? If so how because it doesn’t show up
-
@jmartin1009 sure
cd ~ npm uninstall rrule
-
@sdetweil how do i fix this?
pi@raspberrypi:~/MagicMirror $ npm install rrule npm WARN acorn-jsx@5.0.1 requires a peer of acorn@^6.0.0 but none is installed. You must install peer dependencies yourself. npm WARN grunt-stylelint@0.10.1 requires a peer of stylelint@^9.0.0 but none is installed. You must install peer dependencies yourself. + rrule@2.6.2 added 2 packages from 2 contributors and audited 2431 packages in 49.239s found 4 vulnerabilities (2 low, 2 high) run `npm audit fix` to fix them, or `npm audit` for details pi@raspberrypi:~/MagicMirror $ npm audit fix npm WARN acorn-jsx@5.0.1 requires a peer of acorn@^6.0.0 but none is installed. You must install peer dependencies yourself. npm WARN grunt-stylelint@0.10.1 requires a peer of stylelint@^9.0.0 but none is installed. You must install peer dependencies yourself. up to date in 51.138s fixed 0 of 4 vulnerabilities in 2431 scanned packages 2 package updates for 4 vulns involved breaking changes (use `npm audit fix --force` to install breaking changes; or refer to `npm audit` for steps to fix these manually)
Thanks for all your help btw
-
@jmartin1009 said in MM won't run, blank screen with cursor showing after updating:
it saysrun
npm audit fix
to fix themmany times you cannot fix them all… so, after one try, ignore it
-
@sdetweil Okay! Do you know anything about MM-voice? having issues with that for some reason and i can’t figure out why.