-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Won't show up #9
Comments
I don't have any coding experience; just reading on this site and putting together my own MM. I had the same problem of module not showing up. All I did was move the "position" code out of the config brackets and nested at the same level as the "module" line (right under it) and that fixed it for me. |
See the readme, your config file should be formatted as follows:
You seem to be missing the "modules" section |
It's actually { |
I cannot get this to work either. Here's my snippet from the config file. I have added a number of other modules that work fine.
|
This module doesn't work - using the latest version of MM (new installation) |
Solved it: It's pointing to a wrong directory. |
the module wont show up for me, idk if im supposed to install it there but i need to with all the other modules and it wont show up but this error came what should i do
Console:
pi@raspberrypi:~/MagicMirror/modules/MMM-CountDown $ npm install
npm WARN grunt-stylelint@0.10.1 requires a peer of stylelint@^9.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN stylelint-config-recommended@2.1.0 requires a peer of stylelint@^8.3.0 || ^9.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN stylelint-config-standard@18.2.0 requires a peer of stylelint@^8.3.0 || ^9.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN MMM-CountDown@1.0.0 No repository field.
audited 439 packages in 24.826s
found 0 vulnerabilities
Config:
{
module: 'MMM-CountDown',
config: {
position: "top_left",
event: "Jahrestag",
date: "2019-07-24"
}
},
The text was updated successfully, but these errors were encountered: