@mumblebaj @sdetweil

I did the update using @sdetweil upgrade script

@mumblebaj
Just hesitant that the update will break other modules my MM is using. Sounds like Node updates could be more hassle than they are worth if your MM is functioning, minus a model or 2 ;)

What is the safest way to update Node to 20.9.0? Node Version Manager?

@sdetweil said in MMM-MovieListings:
Here is what mine shows:

Do you think it is worth updating to Node 22.9.0? What is the safest way to do so?

@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:

@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.

@mumblebaj
v20.18.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

@KristjanESPERANTO I am on v.20.18.0

@mumblebaj Thanks for the response and sorry for the delay on my side.

I am in fact using the latest version:

@mumblebaj Thanks for creating this fork! I cannot seem to get the module to work, however. Here is what I am seeing in the dev console:

Here is my config:

Any ideas? I am using the API Read Access Token instead of the API Key from TMBD, as required per your GitHub.