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.

    module not found error loading module in MagicMirror

    Scheduled Pinned Locked Moved Solved Troubleshooting
    41 Posts 12 Posters 36.5k Views 14 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.
    • kusselinK Offline
      kusselin @sdetweil
      last edited by kusselin

      @sdetweil Hello everyone, I haven’t been here for a while and my Magic Mirror was switched off…after I switched it on again I made updates to the modules via remote…but I still don’t have any display for some modules like Tankerkönig…when I start the Mirror it always says “Modules cannot be loaded”.

      Now, as described by sdetweil, there are commands that you have to execute in the modules in question…but unfortunately I haven’t quite understood how I have to do this in the right order?

      It would be really nice if you could explain to me how I have to proceed in order to display the modules again, such as Tankerkönig or mmm-fuel.

      Thank you very much in advance for your help.

      Greetings

      Kussel

      i don´t understand that here:

      npm install ???
      
      where ??? is the library noted in the message Cannot find module ‘???’
      
      | in the example message above, ??? is request
      
      to find this message, look in the output of npm start. or if you use pm2 to launch mm do
      pm2 logs --lines=50
      

      how do I proceed exactly?

      pi@raspberrypi:~/MagicMirror/modules/MMM-Tankerkoenig $ npm init -y
      Wrote to /home/pi/MagicMirror/modules/MMM-Tankerkoenig/package.json:
      
      {
        "name": "MMM-Tankerkoenig",
        "version": "1.0.0",
        "description": "This is a module for the [MagicMirror²](https://github.com/MichMich/MagicMirror/) which displays a fuel prices from [Tankerkoenig](https://www.tankerkoenig.de/).",
        "main": "MMM-Tankerkoenig.js",
        "scripts": {
          "test": "echo \"Error: no test specified\" && exit 1"
        },
        "repository": {
          "type": "git",
          "url": "git+https://github.com/terenc3/MMM-Tankerkoenig.git"
        },
        "keywords": [],
        "author": "",
        "license": "ISC",
        "bugs": {
          "url": "https://github.com/terenc3/MMM-Tankerkoenig/issues"
        },
        "homepage": "https://github.com/terenc3/MMM-Tankerkoenig#readme"
      
      
      S 1 Reply Last reply Reply Quote 0
      • S Offline
        sdetweil @kusselin
        last edited by

        @kusselin find the messages output by mm

        search the messages for one like shown (without the ???)

        find the name of the library in quotes (now u have ???)

        issue a command using that info

        Sam

        How to add modules

        learning how to use browser developers window for css changes

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

          @sdetweil thank you…it´s working now.

          1 Reply Last reply Reply Quote 0
          • L Offline
            LMAC
            last edited by

            I ran the command as recommended (request was my error as well). I now have this error and MM will not load:

            A JavaScript error occurred in the main process
            Uncaught Exception:
            Error: Cannot find module ‘logger’
            Require stack:

            • /home/pi/MagicMirror/js/app.js
            • /home/pi/MagicMirror/js/electron.js
            • /home/pi/MagicMirror/node_modules/electron/dist/resources/default_app.asar/main.js
            • at Module._resolveFilename (node:internal/modules/cjs/loader:940:15)
              at Function.n._resolveFilename (node:electron/js2c/browser_init:249:1128)
              at Function.Module._resolveFilename (/home/pi/MagicMirror/node_modules/module-alias/index.js:49:29)
              at Module._load (node:internal/modules/cjs/loader:785:27)
              at Function.c._load (node:electron/js2c/asar_bundle:5:13331)
              at Module.require (node:internal/modules/cjs/loader:1012:19)
              at require (node:internal/modules/cjs/helpers:94:18)
              at Object. (/home/pi/MagicMirror/js/app.js:13:13)
              at Module._compile (node:internal/modules/cjs/loader:1116:14)
              at Object.Module._extensions…js (node:internal/modules/cjs/loader:1169:10)
            S 1 Reply Last reply Reply Quote 0
            • S Offline
              sdetweil @LMAC
              last edited by

              @lmac well you ran it in the wrong place… oops

              do this

              cd ~/MagicMirror
              rm -rf node_modules
              rm package-lock.json
              npm install
              

              then for whatever module was causing problem

              cd ~/MagicMirror/modules/modulename
              

              do the same last 3 steps as above
              AND THEN

              npm install request --save
              

              Sam

              How to add modules

              learning how to use browser developers window for css changes

              1 Reply Last reply Reply Quote 1
              • D Offline
                DarrenHill
                last edited by

                Just wanted to say thanks for the fix here.

                Did an update and hit exactly this with MMM-GmailFeed and the request module.

                Installed it back (with an audit fix afterwards) and now all up and running again :)

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

                  @darrenhill said in fix for black screen in 2.16 and later:

                  with an audit fix afterwards

                  don’t do those… many times leave more trouble than they fix…
                  we can’t suppress the audit warning message

                  Sam

                  How to add modules

                  learning how to use browser developers window for css changes

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

                    @sdetweil OK, thanks for the pointer.

                    Always kinda worried when that style of message pops up, for security and suchlike.

                    I see from the update that my node is very much out of date, so now just backing things up before setting the update script onto it to try and bring that up too.

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

                      @darrenhill upgrade is for MM, not node, (altho it might do it, works sometimes, need to move to n) …

                      easiest is using the node version of nvm, called n

                      do

                      sudo npm i n -g
                      PATH="$PATH"
                      n 16 
                      

                      then node 16 will be installed…

                      note that you will have to do another npm install in the mm (and maybe module folders)
                      this the upgrade would do (with force instead of apply)

                      n also allows you to SWITCH versions, or use a particular version for ONE app…
                      see n --help

                      Sam

                      How to add modules

                      learning how to use browser developers window for css changes

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

                        @sdetweil - I did it via your update script, and it has updated Node from v10.x to v16.x (or at least that is what appears to have happened from what I could read).

                        It’s quite an old install that just sits on my desk and largely gets left to its own devices. It is in a PiTop Ceed rather than a true mirror, and basically the only thing it runs is MM (it’s actually a dual-boot via PINN also with RetroPie, but the Raspi OS partition is essentially only MM). So no need to keep things focussed to one app or anything like that - no issue of cross-contamination.

                        All is working fine after the update though, so no problems.

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