Can you help me about this error

[justjim1220]

@fonfon

I had that error a few times, it was always an error in the config.js file. use a Js Linter to help you find the errors.

[Fonfon]

@justjim1220 thanks i use jshint.com no error

[justjim1220]

@fonfon

next thing to try it to npm install in each individual module directory

then npm rebuild in the MagicMagic directory

let me know if that helps!

[Mykle1]

@fonfon

Did you determine which module is causing the error?

[Fonfon]

@mykle1 Thanks mykle1 but no !
for desactivate a module i cut/paste the folder on the desktop then i restart the MM is it the good method ?
because when i have no module its ok no error
only with pir module its good
but after with wunderground or google maps traffic module i have a lot of error or other…
i don’t understand !!
this after the update in 2.4.1.

[Mykle1]

@fonfon said in Can you help me about this error:

is it the good method ?

This is how I disable modules without copying and pasting and moving things around. You can simply add disabled: false, at the beginning of all your config.js entries. true will disable the module.

{
            disabled: false,
            module: 'MMM-EventHorizon',
            position: 'bottom_left',
            config: {
                date: "2018-09-17", // (YYYY-MM-DD)  Date timer will end
                time: "00:01:00", // (HH:MM:SS)    Exact time you want timer to end
                text1: "Lucy's Birthday", // 2 lines of text during timer
                text2: "Tempus Fugit", // 2 lines of text during timer
                endText1: "Lucy is 1 today!", // 2 lines of text when timer ends
                endText2: "What a big girl!", // 2 lines of text when timer ends
            }
        },

[justjim1220]

@fonfon

no need to cut/paste each module…

you can add

   disabled: false

above each module, like this…

{
    disabled: false,
    module: "clock",
    position: "top_center"
},

then, you can change it to true to shut off the module.

it would be the easiest way to determine which module is causing the issue.
load all your modules back into the config.js,
add the code above,
make all the default modules ‘false’,
and all the rest ‘true’,
refresh your mirror,
if you still get the same issues,
turn off the mirror and your terminal,
maybe even restart your computer,
then open your terminal,
restart the mirror with ‘npm start -dev’
this will give you an error log, find that and post it in here,
this would be easier for us to help you

[justjim1220]

@mykle1

LMAO!

I was posting my reply when yours popped up! :winking_face:

[justjim1220]

@fonfon

[Mykle1]

@fonfon

I’d like to see any errors from your terminal and/or your console