So in adding the calendar functionality to the module, my goal was to make it (and the ical-generator dependency) optional so that those who didn’t wish to use it could simply clone the repo, add the basic config and be up and running. Whereas those who wanted the calendar, could go through the additional npm install
steps.
I tested this with the following set up:
- On my Dev machine, I have the
ical-generator
package installed. Here I can set thecalendar
configuration option to true or false and the module works without error - On my Pi, the
ical-generator
package has never been installed. Setting thecalendar
option to false, allows the standings table to be displayed, but setting it totrue
triggers an error. Furthermore, omitting thecalendar
option from the config also triggered an error.
On investigation the default value for the calendar
option was set to true. Thus always forcing the ical-generator
package to be required. I’ve updated the code to correctly set the default to false and now the Pi instances works as expected without the package if the option is not set in the config and if it set to false .
Could it be that in your instance, the config for MMM-Forumla1 did not include the calendar option, therefore, the module failed?
Perhaps someone could confirm this by running npm uninstall ical-generator
in the module folder, then git pull
to get the latest version of the module, then set calendar: false
in the config options and see if the standings display?