MMM-MovieListings

[sdetweil]

@BerkSmash1984 when u start mm, npm start

we added messages that dump the runtime env

from my linux system

[2024-10-07 13:14:07.805] [INFO]  System information:
### SYSTEM:   manufacturer: System manufacturer; model: System Product Name; virtual: false
### OS:       platform: linux; distro: Ubuntu; release: 22.04.4 LTS; arch: x64; kernel: 5.15.0-122-generic
### VERSIONS: electron: 31.6.0; used node: 20.17.0; installed node: 22.9.0; npm: 10.8.3; pm2: 5.4.2
### OTHER:    timeZone: America/Los_Angeles; ELECTRON_ENABLE_GPU: undefined 

[BerkSmash1984]

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

[sdetweil]

@BerkSmash1984 no. not worth it

[mumblebaj]

@BerkSmash1984 I would give node 20.9.0 a go.

[BerkSmash1984]

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

[mumblebaj]

@BerkSmash1984 Yeah, that would work.

[sdetweil]

@BerkSmash1984 if you used my script it should upgrade mode too. it uses n, the nodejs version of nvm

[mumblebaj]

@sdetweil From the above it does seem like he used your script but it failed to update node to the required version which should be one of the following, right?

>=20.9.0 <21 || 22

[sdetweil]

@mumblebaj yes , id like to see the installers/upgrade.log
maybe the test subversion failed

[sdetweil]

@mumblebaj really >=20.9.0, not 21, or >= 22

[mumblebaj]

@sdetweil From package.json

[BerkSmash1984]

@mumblebaj @sdetweil

I did the update using @sdetweil upgrade script

[mumblebaj]

UPDATES

V1.1.0

• Fixed issue with cast list appending cast members from different movies to the same list. Now only cast members of the displayed movie is displayed.
• Update and simplify the API calls to reduce the number of calls.