@imchrisrein Which Module are you using?

@edubey I am working on my own module, and saw this post. I too am interested in knowing the answer to this. If not, I would also be curious to your solution.

@ninjabreadman++ Thank you again for your reply, I will review the MM on the pi0w with the dir name the same as the Module.register(). That said, if this is truly the issue, wouldn’t the same issue persist when booting up the electron app locally on my mac?

re loader.js error that appears to be coming from MagicMirror/js/loader.js which appears to be failing to load my MMM-my-module.js file AFAIK

@johnnewhouse Could/Would you mark my last post as the answer? Not sure if you saw my previous comment, as I edited the post to @ you :)

Hello @ninjabreadman, thank you for your reply.

Yes, my magic mirror, running on my pi0w indeed starts up. Once I added a custom module I am building, it no longer starts up. I get the Black screen.

I checked the config via ssh and nano, it all looks good.
My Module folder is:

• MMM-MY-module
  –MMM-my-module.js

Module.register("MMM-my-module"..

when I comment out my module, everything works. I checked and dbl checked that the MMM-my-module.js does NOT have any es6 (known issue for raspberry pi0w in it. There IS es6 in the node_module_helper.js but that should be moot since that is processed server side.

Thoughts?

Having issues with module development. Everything works fine when starting the app locally. However, when I push my code to my raspberry Pi0w an start it up, I get the following error:

pi@magic-mirror:~ $ sudo xinit /home/pi/midori_start.sh


X.Org X Server 1.18.4
Release Date: 2016-07-19
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.26-v7+ armv7l Raspbian
Current Operating System: Linux magic-mirror 4.14.62+ #1134 Tue Aug 14 16:58:07 BST 2018 armv6l
Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1200 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:B4:99:96 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=PARTUUID=6034293c-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait modules-load=dwc2,g_ether
Build Date: 11 November 2016  11:59:59AM
xorg-server 2:1.18.4-2+rpi1 (https://www.debian.org/support) 
Current version of pixman: 0.33.3
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Aug 27 17:56:14 2018
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
modprobe: FATAL: Module g2d_23 not found.
wm_set_cursor_visibility: visible using XCreateFontCursor
** Message: console message: [native code] @0: Initializing MagicMirror.

** Message: console message: [native code] @0: Loading core translation file: translations/en.json

** Message: console message: [native code] @0: Loading core translation fallback file: translations/en.json

** Message: console message: [native code] @0: Load script: modules/MMM-my-module//MMM-my-module.js

** Message: console message: http://localhost:8080/js/loader.js @190: Error on loading script:

** Message: console message: [native code] @0: Load stylesheet: css/custom.css

** Message: console message: [native code] @0: All modules started!

@johnnewhouse the issue is in the for loop the keyword that is used is an ES6 variant: the let keyword. Flip it to var and voilá, golden!

i.e.:

listContainsEvent: function(eventList, event){
	for(var evt of eventList){
		if(evt.title === event.title && parseInt(evt.startDate) === parseInt(event.startDate)){
			return true;

Edit: I submitted a PR to fix this:
https://github.com/MichMich/MagicMirror/pull/1381