Read the statement by Michael Teeuw here.
MMM-MovieListings
-
@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 -
@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 -
@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 no. not worth it
-
@BerkSmash1984 I would give node 20.9.0 a go.
-
@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?
-
@BerkSmash1984 Yeah, that would work.
-
@BerkSmash1984 if you used my script it should upgrade mode too. it uses n, the nodejs version of nvm
-
@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 -
@mumblebaj yes , id like to see the installers/upgrade.log
maybe the test subversion failed
