Read the statement by Michael Teeuw here.
Upgrade errors?
-
@croc_dad72 @BKeyport and any others… I screwed up for the non-buster systems…
please try my scripts again… they should FIX the problems encountered…
I remove the current node and then install the correct… 18 for buster, 20 for bullseye
-
@sdetweil It does seem to work again on latest.
-
I also had this problem, using Buster on a Raspberry pi 3b.
It started with my npm being to old, unable to upgrade because my node was to old.
Installing the newest node gave me the `GLIBCXX_3.4.26’ not found (required by node) error.The solution for me was installing the LTS version of node using nvm.
nvm install 'lts/*' --reinstall-packages-from=current nvm alias default 18this uses node version 18.
after that I could upgrade npm
nvm install-latest-npmand with all this in place the upgrade of magic mirror worked.
Hope this helps
-
@sdetweil I tried to run the upgrade script on my RPI 4B running Bullseye and it hosed my MM. During the install, I see this:
It appears to have removed/partially remove npm altogether:
Any thoughts?
-
@BKeyport said in Upgrade errors?:
Cannot find module ‘fetch’
we removed this in 2.25
see
https://forum.magicmirror.builders/topic/15778/fix-for-black-screen-in-2-16-and-lateror, you can comment out the require in the module node_helper.js
as fetch is built in in 2.18 and up
-
@BerkSmash1984 I see 64bit… let me look
seems the process is different there… darn
-
@sdetweil Can you help me fix my WSL? I seem to be having and issue with electron and a missing lib. I have emailed you the install.log as well.
-
-
@sdetweil Thanks Sam. A bunch of missing libs but all working again.
Now to add my modules I had running on the dev machine. The joy. :-)
-
@mumblebaj always backup
I have one that makes a small image
https://github.com/sdetweil/MagicMirror-backup-restore
