Read the statement by Michael Teeuw here.
Quick Syntax Error
-
@smartsoldier
I’ve copied your configuration and tried. but there was no syntax error.{ module: 'MMM-DropboxWallpaper', position: 'fullscreen_below', // fullscreen_below is the best position. classes: "default everyone", // when you use MMM-ProfileSwitcher. config: { refreshInterval: 1000*60, search: [".jpg", ".png", ".gif"], // Or you can find target files like "PARTIAL FILENAME". (wildcard or regexp not supported) directory: "/MyMirror", // root of directories of Dropbox to be scanned. sort: "random", //"time09", "time90", "nameAZ", "nameZA", "random" tokenLocationIQ : "", // See http://locationiq.org/#register dropboxAccessToken: "", width: "100%", // 'px' or '%' or valid value for CSS dimensions units. height: "100%", mode: "contain", // 'cover', 'contain', 'hybrid' or any other values for CSS `background-size` dateTimeFormat: "HH:mm MMM Do, YYYY", // See. moment.js .format() } },
-
I would try changing this:
tokenLocationIQ : "secret",
to this:
tokenLocationIQ: "secret",
-
I tried taking out the comma after YYYY, and moving the : closer to tokenLocationIQ. Neither worked. I’m not really sure how Sean managed to run without syntax errors when I am using the exact same config…
-
@smartsoldier I’ve copied from your post and nothing changed except some private values(tokens)
-
@smartsoldier
Most of the syntax errors could be raised by missing or exceeding bracket, comma.
I suggest you remove configuration of modules one-by-one and try.
Or you should upload a completeconfig.js
here. -
I also do not get an error when copy/pasting your config lines.
$ npm run config:check
does not give an error.
You should try it yourself; a very useful command.
Perhaps the error does not apply to the MMM-DropboxWallpaper config ? -
Ok well I used npm run config:check and it found no errors, but I still get the syntax error message is red when I start up the MM. What is happening!??!
-
@smartsoldier We don’t know. Remove all the modules in
config.js
and add one-by-one. Let’s see what happens. -
@sean If I remove this module everything runs fine, then if I put it back this happens. Does that mean its this module or no?
-
Are you willing to share the syntax error with us?
I thought you were referring to the “create config file” message at startup.