Read the statement by Michael Teeuw here.
Can't get MM to start, says it can't find electron, then electron won't start
-
@sdetweil another error, it says
npm ERR! file /home/pi/MagicMirror/package.json npm ERR! code EJSONPARSE npm ERR! JSON.parse Failed to parse json npm ERR! JSON.parse Unexpected end of JSON input while parsing near ' ' npm ERR! JSON.parse Failed to parse package. json data. npm ERR! JSON.parse package.json must be actual JSON, not just JavaScript. -
@jmartin1009 did u download the MagicMirror folder over again?
-
@sdetweil yes I deleted the contents of the old folder and changed the name and redownloaded MagicMirror
-
@jmartin1009 ok, from the /home/pi folder lets start again
cd ~ rm -rf whatever_the_old_folder_name_is rm -rf MagicMirror git clone https://github.com/MichMich/MagicMirror.git cd MagicMirror npm install -
@sdetweil okay I did all of that and it said it cloned and everthing, and then it rebooted during the install, now what? lol
-
@jmartin1009 should not reboot
-
@sdetweil oh it reboots everytime I install magicmirror, how do I prevent this? because it always reboots like 1/3 of the way through the progress bar and it always did it so I thought it was normal lol can I stop this? I have a pi 3+ btw
-
@jmartin1009 it also does that everytime I try to install electron so maybe that’s why it isn’t working :confused: is there any fix for this?
-
Sorry, I do not know. Mine never reboots.
How big is your memory card?
-
@sdetweil 32 gb
-
@sdetweil I believe u figured out why it was restarting, a common cause of it is lack of power, and some person had problems with their keyboard drawing too much power so I unplugged it and it went all the way through without rebooting, but I still got some issues, im left with
Installing dependencies ... npm WARN deprecated time-grunt@2.0.0: Deprecated because Grunt is practically unmaintained. Move on to something better. This package will continue to work with Grunt v1, but it will not receive any updates. npm WARN deprecated nomnom@1.8.1: Package no longer supported. Contact support@npmjs.com for more info. npm WARN tarball cached data for async@~1.5.2 (sha1-7GphrlZIDAw8skHJVhjiCJL5Zyo=) seems to be corrupted. Refreshing cache. 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. 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 ERR! path /home/pi/MagicMirror/node_modules/coffeescript/bin/coffee npm ERR! code ENOENT npm ERR! errno -2 npm ERR! syscall chmod npm ERR! enoent ENOENT: no such file or directory, chmod '/home/pi/MagicMirror/node_modules/coffeescript/bin/coffee' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent npm ERR! A complete log of this run can be found in: npm ERR! /home/pi/.npm/_logs/2019-02-20T04_31_21_244Z-debug.log Unable to install dependencies! -
@jmartin1009 I think u need to restart the install
Erase the node_modules folder, and do it again
-
@sdetweil I erased node_modules and reinstalled magicmirror and got this
Cloning MagicMirror Done! Installing dependencies ... npm WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning ENODATA: Cache input stream was empty npm WARN registry Using stale package data from https://registry.npmjs.org/ due to a request error during revalidation. npm ERR! code EINTEGRITY npm ERR! errno EINTEGRITY npm ERR! Invalid response body while trying to fetch https://registry.npmjs.org/feedme: Integrity verification failed for sha512-neorTWnU+xIGoFGw5xKt8oa6Zrp4OIAdLKdTJkmTvESrU1kHYWBEQbxKaFtPAPPX7OiREkBnp0E0/gPN4QnmQg== (/home/pi/.npm/_cacache/content-v2/sha512/9d/ea/2b4d69d4fb1206a051b0e712adf286ba66ba7838801d2ca753264993bc44ab53590761604441bc4a685b4f00f3d7ece891124067a74134fe03cde109e642) npm ERR! A complete log of this run can be found in: npm ERR! /home/pi/.npm/_logs/2019-02-20T17_49_38_341Z-debug.log Unable to install dependencies!What do I do now?
-
from the /hom/pi folder do
rm -rf .npm cd MagicMirror rm -rf node_modules npm install -
@sdetweil I am now given this, what do I do next?
MagicMirror installation successful! > magicmirror@2.6.0 install-fonts /home/pi/MagicMirror > cd fonts && npm install added 1 package from 1 contributor and audited 1 package in 5.243s found 0 vulnerabilities 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. 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. added 930 packages from 1367 contributors and audited 2433 packages in 160.197s found 23 vulnerabilities (8 low, 14 moderate, 1 high) run `npm audit fix` to fix them, or `npm audit` for details -
@jmartin1009 if your mirror is not accessible from the internet I would not worry about these vulnerabilities.
-
@sdetweil does that mean I can’t use any modules that use the internet? im using ssh to do these codes and I plan to use alexa and stuff with it so it will require internet use, so what did you mean by that?
-
@jmartin1009 good point. I would run npm audit to get a list of the issues. These generally end up being challenging to solve completely.
-
@sdetweil I ran the audit and then I ran the audit fix and I got this:
found 23 vulnerabilities (8 low, 14 moderate, 1 high) in 2433 scanned packages run `npm audit fix` to fix 13 of them. 8 vulnerabilities require semver-major dependency updates. 2 vulnerabilities require manual review. See the full report for details. pi@raspberrypi:~/MagicMirror $ npm audit fix -bash: pm: command not found 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. + jshint@2.10.1 added 4 packages from 4 contributors, removed 7 packages and updated 13 packages in 39.446s fixed 13 of 23 vulnerabilities in 2433 scanned packages 2 vulnerabilities required manual review and could not be updated 1 package update for 8 vulns involved breaking changes (use `npm audit fix --force` to install breaking changes; or refer to `npm audit` for steps to fix these manually) ╭───────────────────────────────────────────────────────────────╮ │ │ │ New minor version of npm available! 6.4.1 → 6.8.0 │ │ Changelog: https://github.com/npm/cli/releases/tag/v6.8.0 │ │ Run npm install -g npm to update! │ │ │ ╰───────────────────────────────────────────────────────────────╯what should I do now?
-
@jmartin1009 I would see what that 1 high priority issue is.
At the bottom it says some breaking changes required to fix one issue. Breaking changes mean other code needs to be changed. So I would stay away from that fix
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login