I did not know that about the default updatenotification module. Good to know.

I have that module in my config.js with no config options, so I am running the default options. And I have not seen it put up a notification if there was a newer commit on one of the modules (which was the case). In my case that one module that had a newer commit was in my modules directory but not used in config.js, so looking at useModulesFromConfig option, I assume that module was not looked at. So it all makes sense.

I did put in a pull request to tweak wording in updatenotification.md

Cheers

Sounds good. Totally new to this world of MM. My efforts on these modules started when I saw someone post in the “Show Your Mirror” folder that they created a custom module to check for apt updates, but they did not include the module. So I figured I would create one.

Cheers

Never said it was useful (except to myself :)).

But to be clear, MMM-ModuleUpdateNotifier will inform the user if a module they are using has an update (and therefore the developer is active). So it does notify the user of an actionable thing.

Either way, the two modules are out there in the wild now. If people have suggestions, they can interact with the projects on github or ignore them if not useful for them.

For me, it was an interesting opportunity to do some AI-assisted coding in a language that I have not used before and to get back into Linux a little.

Cheers

@sdetweil I am not an expert in that area at all. The follow are some general thoughts:

1. Assume the developer must have listed the needed packages in the dependencies part of the package.json. Not sure how a dependency would not be listed. (Stating the obvious here)
2. If the developer used the cavet such as “^1.2.3”, and you are asking how to update to a newer major version of the dependency, I would say you should work with the development on their module’s github page. Of course, you could also update the package.json file and run “npm install”, and then see if things still work correctly. Be aware that I do not think that my MMM-ModuleUpdateNotifier would have informed of you this issue as it is just looking to see if new commits in github for the modules.

Doubt the above helps.

I guess I could update MMM-ModuleUpdateNotifier to also run “npm install --dry-run” and somehow incorporate that into the notification to the user. That would align with my intent which was to let me know if I had any maintenance to perform on my MM.

Per https://github.com/MagicMirrorOrg/MagicMirror/wiki/3rd-Party-Modules, I am presenting the two modules that I added to the list.

One provides a message if there are system apt packages available for install. The other does a similar thing for MagicMirror module updates.

Freely admit that I used AI for some of the scripting.