Read the statement by Michael Teeuw here.
Added MMM-ModuleUpdateNotifier and MMM-AptUpdateNotifier
-
@CrashTest so, how would a user fix modules which have updated libs, not listed in their package.json dependencies list?
-
@sdetweil I am not an expert in that area at all. The follow are some general thoughts:
- 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)
- 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.
-
@CrashTest you assume the developers are active and interested in doing dependency updates for no particular reason . ( many w breaking changes)
Most developers are not active on the forums.
Anyhow I don’t think the module one is particularly helpful for users. As it sets off a fire alarm with no resolution.
In my humble opinion -
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
-
@CrashTest Our updatenotification module does that for the active modules… same as for MM base
I wasn’t talking about that one
I’m the moderator here, so just watching out for our users… -
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
-
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
-
@CrashTest awesome effort!
-
@CrashTest I saw update for the doc
It should automagically put up an update banner for all
Modules in config.js if their git GitHub ( source repo) commit status changesIt as also outputs messsges where npm start is logged as it scans the repository
