some modules are not showing on screen

A Former User

Its the same like a mouse connected. Sure I can connect a monitor and mouse+keyboard, but I dont know how to get to the dev window. I dont coded anything on the pi directly (like I am using visual code at windows for example). So how to get the dev-output?

sdetweil

@stephen on your remote console, do

ssh to the pi, no gui

cd MagicMirror
export DISPLAY=:0
npm start dev

and, of course, you need a monitor on the PI

A Former User

Thanks!
I’ve connected a monitor and keyboard. Connected via ssh and started like you’ve posted.

Uh great output. Never seen :) … but I am not a node-nerd yet. Anyway…

There are errors to the modules I’ve missing.

In every case there is an error loading the skripts. In the log I saw there is a “/” too much while executing. For example:
GET http://0.0.0.0:8080/modules/internet-monitor//internet-monitor.js

Same at the other modules. But why? Where to correct this?

A Former User

Oh I saw its on all the paths (the running also).
But the error at all the modules are

ERROR on loading script XYZ

The scripts are in the given folder.

sdetweil

@stephen a file system problem again.

U need to run fsck , the Unix chkdsk.
But u can’t run on the boot drive while system is running …

Google search ‘fsck raspberry pi’

I have another Linux system i can use.

A Former User

oh lord… I quess I have something…
WTF.

I quess it was my mistake… Was it?

Some modules are in /MagicMirror/node_modules/
and some are in /MagicMirror/modules

sdetweil

@stephen node_modules are the ones download by install in support of the mirror… all good

modules are the add ons to the MagicMirror

A Former User

Maybe it has something to do with the

npm install

sometimes I had to run (as discribed at the mod-pages)?

I’ll try to pull the modules in the right folder and give it a try

sdetweil

@stephen no… don’t change anything… npm install built the node_modules folder… it is ok…

A Former User

Hell…thats it!

I’ve reinstalled the “not-working” / not showing modules INTO the /modules folder and it simply works!

Have a big thanks @sdetweil !

Its not always a filesystem-problem, sometimes the problem is right in front of the keyboard :D