Read the statement by Michael Teeuw here.
MMM-MovieListings
-
@mumblebaj Thanks for the response and sorry for the delay on my side.
I am in fact using the latest version:
-
@KristjanESPERANTO I am on v.20.18.0
-
@BerkSmash1984 Which version of MM are you running?
MM requires a minimum version of 20.9.xx. Yours is currently lower.
⚠️ This release needs nodejs version v20 or v22, minimum version is v20.9.0.
-
@mumblebaj I am on v2.25.0, not the latest, but the one before the latest, I think.
All other modules are working great.
I can update to the latest, just don’t want any modules to break. I have 10 unique pages showing multiple modules
-
@BerkSmash1984 And which node version? You can run
node -v -
@mumblebaj
v20.18.0 -
@BerkSmash1984 I am not sure what updating node would do to your 2.25.0 version of MM. I assume it should be fine. I updated the module using node 20.9.0. I unfortunately do not have an older version of MM running. My dev machine runs the latest version.
@sdetweil Would MM v2.25.0 run fine with node 20.9.0? I am hoping you may have the answer at hand.
-
@mumblebaj
I am assuming @sdetweil’s MM update script will also update node? I am happy to give that a go if so. I can easily make a backup for my MM to my local machine just in case. -
@BerkSmash1984 updated to latest MM version via @sdetweil upgrade script but looks like it did not touch the Node version. All modules function post update with the exception of the of the MMM-MovieListings module.
Also, it states a Node update is not necessary:
-
@BerkSmash1984 said in MMM-MovieListings:
I can update to the latest, just don’t want any modules to break. I have 10 unique pages showing multiple modules
use my backup/restore scripts
and install/upgrade scripts
