@rkorell said in MMM-Remote-Control:
npm ci
be careful… the package.json was built and tested on a cloud based virtual machine.
pi and other hardware types MAY need a different version of a dependency, i’ve only seen it myself twice in 6 years, but
npm ci uses the exact package.json
npm install will get the appropriate for this platform, even if the version changes.
anyhow… I use npm install --omit=dev when I do the installs script or MMM-Config
@rkorell I was just about to add that you needed to redo the npm install for the module after deleting the node_modules folder
else you were trying to run the new dependencies with the old code
but you fixed it…
@rkorell if you pull the tags, you can use the tag name
git checkout v3.3.2
@rkorell can you tell me when old was? luckily this module uses tags for releases, so you could restore to one of the previous releases…
in the module folder do
git fetch --all --tags
then when we figure out which release to try, we can
git checkout <tag_name>
Release 3.2.1 was about 5 months ago.
@rkorell said in MMM-Remote-Control:
would one of these versions be installed by your current upgrade-scrip
today it will install node 22.18.0
after Jan 1 (2 weeks away) it will install 22.21.1 (for the next release)
@rkorell force was if you already had started installing MM and had the latest code… NOT if you have code changes
the upgrade will report if files are changed and allow you to save them in git. but generally its intended to remind you where you made changes and do something about it…
the node upgrade should not impact the running MM… (I say that with ’ quote marks, cause I am not sure…)
WHY do you NEED the RemoteControl update?? if you don’t NEED it, then don’t take it…
@bicolorbore586 the module code you have used the global variable document to examine the web page contents
The syntax checker found the use, but didn’t know that this code (config.js is a JavaScript file) was loaded in a browser
So it reported use of an undeclared variable
The fix was to declare the variable as a global so the checker will be happy
@rkorell you can only upload pics here, you can paste some of the log into a message ( use the code block )
@rkorell to upgrade node use one of the tools
nvm or n
I prefer n
stop MagicMirror if running
sudo npm install n -g
sudo n 22.18
hash -r
node -v
Should confirm node is upgraded
Now we need to fix the MagicMirror dependencies
cd ~/MagicMirror
rm -rf node_modules
npm install
Then start MagicMirror
In the future, if you want to upgrade MagicMirror, use my upgrade script and it will also upgrade node if necessary
@rkorell said in MMM-Remote-Control:
Node.js v20.18.1
@rkorell Thanks for the feedback and the good error description! I’ll optimize the error logging, but unfortunately you have to update to at least node 22. I recommend version 24.
For the current MagicMirror version, you also need at least version 22.
