MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.

    Update to MagicMirror² v2.7.0 fails

    Scheduled Pinned Locked Moved Tutorials
    6 Posts 3 Posters 2.6k Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S Offline
      sdetweil @drfukc
      last edited by

      @drfukc erase those two files

      git pull, then npm install in MM, and then each module that has a package.json file

      Sam

      How to add modules

      learning how to use browser developers window for css changes

      1 Reply Last reply Reply Quote 0
      • D Offline
        drfukc
        last edited by

        @sdetweil
        partially it worked though the upgrade still terminates with this error message after running “sudo npm install” in the MM directory and all external modules that have a package.json file.
        However, all of these have prompted me that they are already up-to-date.

        These are my steps:

        pi@magicmirror:~/MagicMirror $ sudo npm install
        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 tar ENOENT: no such file or directory, open '/home/pi/MagicMirror/node_modules/.staging/eslint-8983ee3d/LICENSE'
        npm WARN tar ENOENT: no such file or directory, open '/home/pi/MagicMirror/node_modules/.staging/eslint-8983ee3d/README.md'
        
        ... tons of similar WARNINGS in between ... and removed here for better removed for better readability
        
        npm WARN tar ENOENT: no such file or directory, open '/home/pi/MagicMirror/node_modules/.staging/lodash-9ecaa656/lastIndexOf.js'
        npm WARN tar ENOENT: no such file or directory, open '/home/pi/MagicMirror/node_modules/.staging/lodash-9ecaa656/LICENSE'
        npm WARN tar ENOENT: no such file or directory, open '/home/pi/MagicMirror/node_modules/.staging/lodash-9ecaa656/lodash.js'
        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.
        
        npm ERR! err.code.match is not a function
        
        npm ERR! A complete log of this run can be found in:
        npm ERR!     /root/.npm/_logs/2019-04-05T07_27_16_446Z-debug.log
        

        now I check “2019-04-05T07_27_16_446Z-debug.log” but unfortunately this does not help me either:

        842 silly saveTree ├── valid-url@1.0.9
        842 silly saveTree └─┬ walk@2.3.14
        842 silly saveTree   └── foreachasync@3.0.0
        843 warn acorn-jsx@5.0.1 requires a peer of acorn@^6.0.0 but none is installed. You must install peer dependencies yourself.
        844 warn grunt-stylelint@0.10.1 requires a peer of stylelint@^9.0.0 but none is installed. You must install peer dependencies yourself.
        845 verbose stack TypeError: err.code.match is not a function
        845 verbose stack     at BB.try.catch.err (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/with-tarball-stream.js:110:55)
        845 verbose stack     at tryCatcher (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
        845 verbose stack     at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:512:31)
        845 verbose stack     at Promise._settlePromise (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:569:18)
        845 verbose stack     at Promise._settlePromise0 (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:614:10)
        845 verbose stack     at Promise._settlePromises (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:690:18)
        845 verbose stack     at _drainQueueStep (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:138:12)
        845 verbose stack     at _drainQueue (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:131:9)
        845 verbose stack     at Async._drainQueues (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:147:5)
        845 verbose stack     at Immediate.Async.drainQueues (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:17:14)
        845 verbose stack     at runCallback (timers.js:794:20)
        845 verbose stack     at tryOnImmediate (timers.js:752:5)
        845 verbose stack     at processImmediate [as _immediateCallback] (timers.js:729:5)
        846 verbose cwd /home/pi/MagicMirror
        847 verbose Linux 4.14.98-v7+
        848 verbose argv "/usr/bin/node" "/usr/local/bin/npm" "install"
        849 verbose node v8.11.1
        850 verbose npm  v6.9.0
        851 error err.code.match is not a function
        852 verbose exit [ 1, true ]
        

        When opening MagicMirror it looks like I have v2.7.0 installed, since the upgrading message has disappeared and things seem functional.

        However my feeling is that the upgrade is just in the middle of somewhere, though the mirror is working.

        Cheers
        ukc

        1 Reply Last reply Reply Quote 0
        • S Offline
          sdetweil
          last edited by

          you should not have done sudo npm install… this does the setup as root… which will cause problems later

          also, looks like npm is downlevel , so do
          all these from the MagicMirror folder

          npm -v
          npm install -g npm 
          npm -v
          

          this will show old and new versions

          then

           sudo rm -rf node_modules
          

          and then

          npm install
          

          again

          Sam

          How to add modules

          learning how to use browser developers window for css changes

          1 Reply Last reply Reply Quote 0
          • D Offline
            drfukc
            last edited by

            Hi Sam,
            thanks for your support, but unfortunately this takes me to the next issue when executing:

            pi@magicmirror:~ $ npm -v
            6.9.0
            
            pi@magicmirror:~/MagicMirror $ npm install -g npm
            npm WARN checkPermissions Missing write access to /usr/lib/node_modules
            npm ERR! path /usr/lib/node_modules
            npm ERR! code EACCES
            npm ERR! errno -13
            npm ERR! syscall access
            

            After, I changed permissions for /usr/lib/node_modules, but it simply took me to the next error.
            I think I will re-start from scratch.
            Cheers
            ukc

            1 Reply Last reply Reply Quote 0
            • DæmonEyesD Offline
              DæmonEyes
              last edited by

              Check out this thread: https://forum.magicmirror.builders/topic/10212/update-help
              @thedoorsfanatic helped me fix this problem on mine.

              1 Reply Last reply Reply Quote 0
              • 1 / 1
              • First post
                Last post
              Enjoying MagicMirror? Please consider a donation!
              MagicMirror created by Michael Teeuw.
              Forum managed by Sam, technical setup by Karsten.
              This forum is using NodeBB as its core | Contributors
              Contact | Privacy Policy