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.

    Default Weather module still not displaying

    Scheduled Pinned Locked Moved Solved Troubleshooting
    39 Posts 6 Posters 13.3k Views 6 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 @Jarhead96097
      last edited by sdetweil

      @Jarhead96097

      this is on pi, or windows, or ??

      ok, do this

      cd ~/MagicMirror
      rm -rf node_modules
      npm install 
      #added
      git checkout modules/default/weather/weather.js
      git status
      

      then try again

      Sam

      How to add modules

      learning how to use browser developers window for css changes

      S Jarhead96097J 2 Replies Last reply Reply Quote 1
      • B Offline
        Blackeye @Jarhead96097
        last edited by

        @Jarhead96097 Could be the comma after “true” on the last line of config … not necessary, and causes an error when I run a :check

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

          @Jarhead96097

          I added a command above to restore the original weather.js from the git repo

          Sam

          How to add modules

          learning how to use browser developers window for css changes

          Jarhead96097J 1 Reply Last reply Reply Quote 0
          • Jarhead96097J Offline
            Jarhead96097 @sdetweil
            last edited by

            @sdetweil I added “npm audit fix” as there was 1 high severity vulnerability found. It didn’t solve the vulnerability (didn’t try “npm audit fix --force”), and I’m getting the same error.

            Jarhead96097

            S mumblebajM 2 Replies Last reply Reply Quote 0
            • Jarhead96097J Offline
              Jarhead96097 @sdetweil
              last edited by

              @sdetweil Oh, okay. Let me try that updated string of commands…

              Jarhead96097

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

                @Jarhead96097 please never do audit… causes more problems than it fixes

                Sam

                How to add modules

                learning how to use browser developers window for css changes

                Jarhead96097J 1 Reply Last reply Reply Quote 2
                • mumblebajM Offline
                  mumblebaj Module Developer @Jarhead96097
                  last edited by

                  @Jarhead96097 Rule of thumb is to never run npm audit fix.

                  Check out my modules at: https://github.com/mumblebaj?tab=repositories
                  Check my blog-post: https://mumblebaj.xyz/

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

                    @mumblebaj and we have found npm install parms to turn off the warning coming in next release, and already in my scripts.

                    Sam

                    How to add modules

                    learning how to use browser developers window for css changes

                    mumblebajM 1 Reply Last reply Reply Quote 2
                    • mumblebajM Offline
                      mumblebaj Module Developer @sdetweil
                      last edited by

                      @sdetweil That’s great

                      Check out my modules at: https://github.com/mumblebaj?tab=repositories
                      Check my blog-post: https://mumblebaj.xyz/

                      1 Reply Last reply Reply Quote 0
                      • Jarhead96097J Offline
                        Jarhead96097 @sdetweil
                        last edited by

                        @sdetweil Good to know…that may be the root cause of all of this. After rebuilding my MM on 2.20.0, I did the npm audit fix. If we can’t get to a resolution in the next few minutes, I’ll chalk this up to a learning experience and do another rebuild.

                        Jarhead96097

                        S 1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 3
                        • 4
                        • 2 / 4
                        • 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