Read the statement by Michael Teeuw here.
module not found error loading module in MagicMirror
-
@mumblebaj and then pull off the module name and scan it’s package.json to see if it’s referenced
-
@sdetweil said in fix for black screen in 2.16 and later:
did u npm install request in the mm folder, or in a module folder where there was no package.json, the latter ends up putting it in the mm/node_modules, the same as the former
I installed it the way you suggested. In the two module folders with the addition of package.json (npm init -y) and then npm install request. The MMM-DWD-WarnWeather worked on my mirror from the beginning after updating to MM2.17.
-
I enhanced my upgrade script to do all this for all installed modules…
-
@sdetweil @mumblebaj Thank you two for helping me solve this problem after the last update - I spent a LOT of time looking for the solution that you two helped me (the grep made it easier to find the right modules), the two commands were what fixed it.
Will I have to do this again with the next update?
-
@levon maybe. but if you use my upgrade script, it will do the fixes for you
-
@sdetweil Thanks … I will give this a try next time I’m updating. I thought I had tried it before, but perhaps not. I appreciate you sharing this.
-
@sdetweil I did everything as you said, but …
[17.12.2021 04:05.03.723] [ERROR] WARNING! Could not load config file. Starting with default configuration. Error found: Error: Cannot find module ‘request’
Require stack:- /home/pi/MagicMirror/modules/MMM-bitcoin/node_helper.js
- /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
-
@arena and , what is the module/library u need to install?
-
@sdetweil fiddled all day today and figured out
it turned out I did not install or update the dependencies inside the modulesorry, thanks
-
@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=50how 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" -
@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
-
@sdetweil thank you…it´s working now.
-
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)
-
@lmac well you ran it in the wrong place… oops
do this
cd ~/MagicMirror rm -rf node_modules rm package-lock.json npm installthen for whatever module was causing problem
cd ~/MagicMirror/modules/modulenamedo the same last 3 steps as above
AND THENnpm install request --save -
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 :)
-
@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 -
@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.
-
@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 16then 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 -
@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.
-
@darrenhill cool. thx for the feedback
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login