MM won't run, blank screen with cursor showing after updating



  • When i went to go update, it said i had three files that were preventing it from updating, so i deleted them as i said, was package.json, package-lock.json, and vendor/package.json (I think). After updating, i try to run it and it gives a blank screen with the cursor showing and this is what shows in the terminal.

    pi@raspberrypi:~/MagicMirror $ npm start
    
    > magicmirror@2.8.0 start /home/pi/MagicMirror
    > sh run-start.sh
    
    Starting MagicMirror: v2.8.0
    Loading config ...
    Loading module helpers ...
    Initializing new module helper ...
    Module helper loaded: updatenotification
    No helper found for module: clock.
    WARNING! Could not load config file. Starting with default configuration. Error found: Error: Cannot find module 'rrule'
    Loading module helpers ...
    Initializing new module helper ...
    Module helper loaded: updatenotification
    No helper found for module: clock.
    App threw an error during load
    Error: Cannot find module 'rrule'
        at Module._resolveFilename (module.js:543:15)
        at Function.Module._resolveFilename (/home/pi/MagicMirror/node_modules/electron/dist/resources/electron.asar/common/reset-search-paths.js:35:12)
        at Function.Module._load (module.js:473:25)
        at Module.require (module.js:586:17)
        at require (internal/module.js:11:18)
        at Object. (/home/pi/MagicMirror/modules/default/calendar/vendor/ical.js/node-ical.js:27:13)
        at Object. (/home/pi/MagicMirror/modules/default/calendar/vendor/ical.js/node-ical.js:68:3)
        at Module._compile (module.js:642:30)
        at Object.Module._extensions..js (module.js:653:10)
        at Module.load (module.js:561:32)
    Whoops! There was an uncaught exception...
    { Error: Cannot find module 'rrule'
        at Module._resolveFilename (module.js:543:15)
        at Function.Module._resolveFilename (/home/pi/MagicMirror/node_modules/electron/dist/resources/electron.asar/common/reset-search-paths.js:35:12)
        at Function.Module._load (module.js:473:25)
        at Module.require (module.js:586:17)
        at require (internal/module.js:11:18)
        at Object. (/home/pi/MagicMirror/modules/default/calendar/vendor/ical.js/node-ical.js:27:13)
        at Object. (/home/pi/MagicMirror/modules/default/calendar/vendor/ical.js/node-ical.js:68:3)
        at Module._compile (module.js:642:30)
        at Object.Module._extensions..js (module.js:653:10)
        at Module.load (module.js:561:32) code: 'MODULE_NOT_FOUND' }
    MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
    If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues
    Launching application.
    

    It launched and worked fine beforehand, i was just updating because i was getting an error for some reason with MMM-Voice and thought maybe if i updated it would work.



  • @jmartin1009 after downloading the code (with git pull) , you need to do

    cd ~/MagicMirror
    npm install
    
    

    also, if u have modules other than the default, you must ALSO do
    nom install in each module folder where there is a package.json file present to cleanup the new dependencies

    in the future, i hope my updater script (link to topic below) will be available as part of the package to help solve these kinds of problems…

    https://forum.magicmirror.builders/topic/10859/new-update-upgrade-script-ready-for-testing



  • @sdetweil Thank you for the quick answer! Doing that as we speak.Do you however also have any knowledge about MMM-Voice? Running into an error there as well, that’s what prompted the update. Thanks!



  • @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?



  • @jmartin1009

    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