Testing my module, it is stuck loading

[sdetweil]

@l0zarus AH, now we’re getting somewhere

go to the console tab and put part of your module name in the filter field

also,

modulename in config.js = folder name in modules folder = filename of the .js file
AND the register name

config.js 
     module:"SampleModule", 
modules/SampleModule/SampleModule.js
Module.register("SampleModule", {

ALL these MUST match else your module is not loaded
system is case sensitive

[l0zarus]

@sdetweil Alright I have a few errors showing, and I’m having an issue moving my file to the modules folder. I have verified the name is the same across the folder, the js file, and the config file.

First, I got the following message when trying to move it:

mv MMM-ConcertsAroundMe /modules
mv: cannot move 'MMM-ConcertsAroundMe' to '/modules': Permission denied

Will paste the console errors as well, I am moving between my mac and raspberry pi

[sdetweil]

@l0zarus its not /modules (that is in the root)

depending where your module is , the quick way

mv MMM-ConcertsAroundMe ~/MagicMirror/modules

[l0zarus]

@sdetweil aha! I had tried that as well, but I did not include the ~. I am learning so much from this project :)

[sdetweil]

@l0zarus said in Testing my module, it is stuck loading:

I am moving between my mac and raspberry pi

magicmirror will run on your mac…

use my install script

[sdetweil]

@l0zarus ~ means users home folder (less letters to type, remember most of this linux console stuff was created on slow 300bps phone lines… the fewer letters the better)

[l0zarus]

@sdetweil alright here are the errors:

[sdetweil]

@l0zarus did yiu npm install luxon in your module folder

npm init -y 
npm install luxon 

if u don’t do the npm init in your module folder the module will be installed in the root MM node_modules, then not found here

[l0zarus]

@sdetweil ok that was an issue! I got luxon installed in the right place. Now I’m getting the following errors:

I tested the exact link from the first error “Access to fetch at…” in postman and I get a clean response

[sdetweil]

@l0zarus lovely CORS… welcome to the fun

postman didn’t use localhost it used the local IP address

you ‘might’ get to fix it in config.js ? maybe

from terminal window do

ip addr

that give u the local machine ip address
use that in the config.js

address:""

instead of locahost…

CORS basically means, “hey, you are not in our known approved access network, get lost”