@KristjanESPERANTO Will see if I can get one done for PGA. But heading on holidays tomorrow. Back in the new year.

@levon I think check if it is successfully hitting the API on Strava. Check https://www.strava.com/settings/api.

Also check if the Authorization Callback Domain matches your MM IP.

Handing over the module

I have recently not had time to look after this module and I think that @dathbe will do a much better job looking after the module going forward.

Here is a link to his fork: MMM-PGA. I have updated the 3rd Party Modules to point to his fork.

I will archive my fork of the module this weekend.

@KristjanESPERANTO Stats were great, fixed most of the issues identified in my modules. Majority package.json issues.

Great work @KristjanESPERANTO

@brentmatthews Hi, yes, I did not require a css file for the module. You are welcome to add and submit a pr if you like.

@levon Awesome. Glad you found the issue. The code uses the npm module strava-v3. It looks like the method used does not return walking.

The issue was that I had to specify the lon and lat manually in the config.js.

My 2 cents worth.

@Jalibu I agree with your view.

It is highly recommended you commit the generated package lock to source control: this will allow anyone else on your team, your deployments, your CI/continuous integration, and anyone else who runs npm install in your package source to get the exact same dependency tree that you were developing on.

See npm documentation

@KristjanESPERANTO Personally I always add it to .gitignore along with node_modules folder.

@rkorell Just read that X11 is still there in Trixie. So no stress yet, but yes, it is old and may be on it’s way out one of these good ol days.

@plainbroke There you go. Use the upgrade script by @sdetweil with the apply option and it should sort out your modules’ missing dependencies. If you still have issues then post the logs so we can see what else is wrong.

Maybe this can help some users.

The following will search all *.js files in the modules folder for the reference of request. You can then just enter the module folders and install as per @sdetweil suggestion above. The same can be done for the other missing modules.

grep -r -E '('request')' ~/MagicMirror/modules/*/*.js

or search for multiple problem modules

grep -r -E '('request') | ('valid-url')' ~/MagicMirror/modules/*/*.js

Produces the following:

@KristjanESPERANTO My 20pence/cents worth, I vote to make this the official page. We need to move with the times and the old page is outdated.

@BKeyport X11 does not work for me, hence I use Wayfire. As Labwc is supposed to be the newer lighter compositor, I would like to get that to work for me.

@ankonaskiff17 SO I believe a few things have changed since. Some deprecated modules they got rid off i.e. request and some others. Modules that use them would be a problem. My suggestion would be to use Sam’s upgrade script which would check each module directory and fixup the missing dependencies for you.

@karsten13 So I have been tinkering with the MMM-Hue module a bit and have replaced jQuery which seems to invoke XMLHttpRequest, with node-fetch, albeit the older version (2.6.1) of node-fetch, but it now returns data without requiring a certificate and the use of https.

@BKeyport As an IT person I would say we need to move with the times. Being stuck in the old is never good. Have you tagged your modules as per the stats gathered on it?

@ember1205 Easiest way for me was installing the Adguard plugin on Chrome

@cowboysdude This is so funny…:face_with_tears_of_joy:

@landaisbenj I have seen this error before. It comes from installing the latest version of node-fetch whereas the module uses an older version of node-fetch. The latest version is an ES module and must be import’d instead of require’d in the node_helper.

@BKeyport Gives users an indication that they are outdated and may not be supported. My point is being stuck in the past is never a good idea unless you want your project to “die”