@sdetweil From package.json

@sdetweil Thanks for the assist with this one Sam but my module does list the dependencies on Github. Check it out.
@cowboysdude Same to you too from South Africa.
@levon That message just says that the module will not work on an older version of the mirror. It is not an error. Are there any other errors in NPM? Can you check the developer window for any errors, Do a Ctrl + i which should open the developer window. MMM-Strava seems to be working fine for me.
@swvalenti The issue is in the ESPN.js at line 49 or so. It is looking for defendingChampion.athlete but there isn’t one and it fails. I see you have created an issue on GitHub but sometimes the guys abandon their modules. Maybe the developer responds to you issue. You could change line 49 to the below and it should work.
I would have done it this way:
tournament.defendingChamp = event.defendingChampion ? event.defendingChampion.athlete.displayName : ""

@Rags Welcome to the forum and great start.
Have you tried to run the module and found any issues?
Node_helper.js must be named node_helper.js
Your modules defines a bunch of dependent modules in node_helper.js but none of these were installed when you built the module so anybody who clones the module will not get of the dependent modules installed as they are not mentioned in package,js.
You declare ‘./Logger’ but it is never used. Do you need it?
If you fix the above issues the module starts. I do not run a Docker anywhere but the modules seems to working with the above issues fixed or at least it should get you going.
Always try and run the module first and check for issues and fix them if you can
@mcgroo Have a look at this one.
https://github.com/mumblebaj/MMM-WOTD
has multiple language support etc.
@levon Hi. Apologies for the late replies. Time difference. Can you check when last the tokens.js file was touched? That file is updated every time it does a call out to get data. Else I would suggest maybe just doing a git pull and npm install in the MMM-Strava folder. From the above replies I can’t see anything else that could be going wrong though.
@Rags Need to be bit more specific with what issues you are experiencing. If you are running you mirror with npm start then list the output from npm. Also check the developer console (shift + ctrl+i) and see if there are any errors there.