Read the statement by Michael Teeuw here.
MMM-MovieListings
-
@BerkSmash1984 said in MMM-MovieListings:
I cannot seem to get the module to work
Just an idea: Which node version are you using?
-
@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 -
@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
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login