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.

    MM on Windows - Updated now get black screen

    Scheduled Pinned Locked Moved Solved Troubleshooting
    8 Posts 2 Posters 956 Views 2 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.
    • B Offline
      beachjosh77
      last edited by

      I was running an old version of Magic Mirror on a Windows 10 build and I decided to update my version.
      After updating, I got an error because my package.json still referenced display so I changed it to:

      "main": "js/electron.js",
      	"scripts": {
      		"start": ./node_modules/.bin/electron js/electron.js",
      		"start:dev": ./node_modules/.bin/electron js/electron.js dev",
      

      When I run npm start, I get this:

      PS C:\Users\CompName\MagicMirror> npm start
      npm ERR! code EJSONPARSE
      npm ERR! path C:\Users\CompName\MagicMirror/package.json
      npm ERR! JSON.parse Unexpected token "." (0x2E) in JSON at position 172 while parsing near "...pts\": {\r\n\t\t\"start\": ./node_modules/.bin/..."
      npm ERR! JSON.parse Failed to parse JSON data.
      npm ERR! JSON.parse Note: package.json must be actual JSON, not just JavaScript.
      
      npm ERR! A complete log of this run can be found in:
      npm ERR!     C:\Users\CompName\AppData\Local\npm-cache\_logs\2023-04-17T12_59_59_873Z-debug-0.log
      

      Any help is greatly appreciated!

      S 2 Replies Last reply Reply Quote 0
      • S Offline
        sdetweil @beachjosh77
        last edited by

        @beachjosh77 yes, you STILL have to follow the special windows instructions

        package.json is updated and replaced every release…

        https://docs.magicmirror.builders/getting-started/installation.html#other-operating-systems

        Sam

        How to add modules

        learning how to use browser developers window for css changes

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

          @beachjosh77 yes? you have to do all the install steps again

          manually npm install in fonts and vendors and change package.json.

          see the doc

          Sam

          How to add modules

          learning how to use browser developers window for css changes

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

            @beachjosh77 also, there is a bug, for windows , so you have to get the next version develop branch
            https://forum.magicmirror.builders/topic/14327/testing-new-fixes-or-solving-current-problems-with-next-release-code

            Sam

            How to add modules

            learning how to use browser developers window for css changes

            B 2 Replies Last reply Reply Quote 0
            • B Offline
              beachjosh77 @sdetweil
              last edited by

              @sdetweil Thank you for replying,
              I followed your instructions and ran:

              cd ~/MagicMirror
              git checkout develop
              git pull
              npm install
              

              but I still get

              npm ERR! code EJSONPARSE
              npm ERR! path C:\Users\CompName\MagicMirror/package.json
              npm ERR! JSON.parse Unexpected token "." (0x2E) in JSON at position 181 while parsing near "...ts\": {\r\n\t\t\"start\":  ./node_modules/.bin/..."
              npm ERR! JSON.parse Failed to parse JSON data.
              npm ERR! JSON.parse Note: package.json must be actual JSON, not just JavaScript.
              
              npm ERR! A complete log of this run can be found in:
              npm ERR!     C:\Users\CompName\AppData\Local\npm-cache\_logs\2023-04-17T18_21_14_409Z-debug-0.log
              
              S 2 Replies Last reply Reply Quote 0
              • S Offline
                sdetweil @beachjosh77
                last edited by

                @beachjosh77 yes, you STILL have to follow the special windows instructions

                package.json is updated and replaced every release…

                https://docs.magicmirror.builders/getting-started/installation.html#other-operating-systems

                Sam

                How to add modules

                learning how to use browser developers window for css changes

                1 Reply Last reply Reply Quote 0
                • B Offline
                  beachjosh77 @sdetweil
                  last edited by

                  @sdetweil I forgot to mention, I also ran npm install in fonts and vendors and changed package.json to remove the display again

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

                    @beachjosh77 said in MM on Windows - Updated now get black screen:

                    EJSONPARSE

                    maybe you edited, but you messed it up

                    Sam

                    How to add modules

                    learning how to use browser developers window for css changes

                    B 1 Reply Last reply Reply Quote 0
                    • B Offline
                      beachjosh77 @sdetweil
                      last edited by

                      @sdetweil That worked, thank you!

                      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