Read the statement by Michael Teeuw here.
MM startup problem after update
-
@sdetweil Sam I have an error when I pass the line
git checkout -b temp v.2.27.0pi@MagicMirror:~ $ node -v
v18.20.3
pi@MagicMirror:~ $ cd ~/MagicMirror
pi@MagicMirror:~/MagicMirror $ git fetch --tags
remote: Enumerating objects: 4, done.
remote: Counting objects: 100% (4/4), done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 4 (delta 0), reused 0 (delta 0), pack-reused 0
D▒paquetage des objets: 100% (4/4), fait.
Depuis https://github.com/MagicMirrorOrg/MagicMirror- [nouvelle branche] dependabot/npm_and_yarn/develop/stylistic/eslint-plugin-2.3.0 -> origin/dependabot/npm_and_yarn/develop/stylistic/eslint-plugin-2.3.0
! [rejet▒] v2.17.0 -> v2.17.0 (▒craserait l’▒tiquette existante)
pi@MagicMirror:~/MagicMirror $ git checkout -b temp v.2.27.0
fatal: ‘v.2.27.0’ n’est pas un commit et une branche ‘temp’ ne peut pas en ▒tre cr▒▒e depuis
so I’m not going any further, I’m waiting for your instructions
- [nouvelle branche] dependabot/npm_and_yarn/develop/stylistic/eslint-plugin-2.3.0 -> origin/dependabot/npm_and_yarn/develop/stylistic/eslint-plugin-2.3.0
-
@manu85340 said in MM startup problem after update:
git checkout -b temp v.2.27.0
my fault (that little dot after the v!..) sorry
git checkout -b temp v2.27.0 -
@sdetweil I have an error see below, thanks Sam
pi@MagicMirror:~/MagicMirror $ git checkout -b temp v2.27.0
Basculement sur la nouvelle branche ‘temp’
pi@MagicMirror:~/MagicMirror $ rm package-lock.json
pi@MagicMirror:~/MagicMirror $ rm -rf node_modules
pi@MagicMirror:~/MagicMirror $ npm run install-mmmagicmirror@2.27.0 install-mm
npm install --no-audit --no-fund --no-update-notifier --only=prod --omit=dev/
<— Last few GCs —>[25028:0x4545870] 27358 ms: Mark-sweep (reduce) 226.0 (233.8) -> 225.8 (233.8) MB, 271.2 / 0.0 ms (average mu = 0.812, current mu = 0.296) allocation failure; scavenge might not succeed
[25028:0x4545870] 27592 ms: Mark-sweep (reduce) 226.3 (233.8) -> 226.2 (234.3) MB, 230.3 / 0.0 ms (average mu = 0.653, current mu = 0.018) allocation failure; scavenge might not succeed<— JS stacktrace —>
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
Aborted
pi@MagicMirror:~/MagicMirror $ -
You know, I just realized that the “blank screen” I mentioned earlier was actually just my screen setup. In fact, this is the same errors I was having with the NPM/Node being out of date…
-
-
@manu85340 see this post (and the one before it) in an issue w the same problem
https://github.com/sdetweil/MagicMirror_scripts/issues/89#issuecomment-2176865685 -
@sdetweil hi Sam if I understand correctly it is not possible to restart the MM with the update that I passed, that’s it,
-
@manu85340 I don’t understand.
we have restored back to 2.27
2.28 will not run on buster
you need the next at least bullseye
bur if you are upgrading, go to current, bookworm -
@sdetweil Sam a few posts above I told you that I had a problem passing this line:
git checkout -b temp v.2.27.0 so I didn't pass the other command linesrm package-lock.json
rm -rf node_modules
npm run install-mm -
@manu85340 yes and I replied with the corrected command
https://forum.magicmirror.builders/topic/18838/mm-startup-problem-after-update/30?_=1719933486042 -
S sdetweil referenced this topic on
