Default Calendar Not Loading Events After New MM Update

[angeliKITTYx]

@sdetweil

how do i do percussive maintenance on code xD

kittypi@KITTYpi:~/MagicMirror $ cd ~/MagicMirror
npm run install-mm 

> magicmirror@2.35.0 install-mm
> npm install --no-audit --no-fund --no-update-notifier --only=prod --omit=dev

npm error code EBADENGINE
npm error engine Unsupported engine
npm error engine Not compatible with your version of node/npm: magicmirror@2.35.0
npm error notsup Not compatible with your version of node/npm: magicmirror@2.35.0
npm error notsup Required: {"node":">=22.21.1 <23 || >=24"}
npm error notsup Actual:   {"node":"v22.19.0","npm":"11.13.0"}
npm error A complete log of this run can be found in: /home/kittypi/.npm/_logs/2026-04-28T20_16_16_675Z-debug-0.log
kittypi@KITTYpi:~/MagicMirror $ 

[sdetweil]

@angeliKITTYx the end of your prior log post says 22.21.1 is installed

  installing : node-v22.21.1
       mkdir : /usr/local/n/versions/node/22.21.1
       fetch : https://nodejs.org/dist/v22.21.1/node-v22.21.1-linux-arm64.tar.xz
     copying : node/22.21.1
   installed : v22.21.1 (with npm 10.9.4)  <-----

are you in the same terminal window??
if so, you need

hash -r

to capture the path change

do

which node

so we can see where it it located…

@angeliKITTYx

[angeliKITTYx]

@sdetweil

all the same terminal window. i don’t have anything else open. i know it says 22.21.1, but then node version says 19… very odd.

kittypi@KITTYpi:~/MagicMirror $ hash -r
kittypi@KITTYpi:~/MagicMirror $ which node
/usr/local/node/bin/node
kittypi@KITTYpi:~/MagicMirror $ node --version
v22.19.0
kittypi@KITTYpi:~/MagicMirror $ 

[sdetweil]

@angeliKITTYx ok, close that window and open another and
try the node --version again

[angeliKITTYx]

@sdetweil

closed the terminal, opened a new terminal…

kittypi@KITTYpi:~ $ node --version
v22.19.0
kittypi@KITTYpi:~ $ cd MagicMirror
kittypi@KITTYpi:~/MagicMirror $ node --version
v22.19.0
kittypi@KITTYpi:~/MagicMirror $ 

[sdetweil]

@angeliKITTYx weird
Do

which node

Go to that folder

sudo mv node onode
hash -r
which node
node —version

[angeliKITTYx]

@sdetweil

kittypi@KITTYpi:~/MagicMirror $ cd ..
kittypi@KITTYpi:~ $ which node
/usr/local/node/bin/node
...
kittypi@KITTYpi:/ $ cd usr
kittypi@KITTYpi:/usr $ cd local
kittypi@KITTYpi:/usr/local $ cd node
kittypi@KITTYpi:/usr/local/node $ cd bin
kittypi@KITTYpi:/usr/local/node/bin $ cd node
bash: cd: node: Not a directory
kittypi@KITTYpi:/usr/local/node/bin $ sudo mv node onode
hash -r
which node
node —version
/usr/local/bin/node
node:internal/modules/cjs/loader:1386
  throw err;
  ^

Error: Cannot find module '/usr/local/node/bin/—version'
    at Function._resolveFilename (node:internal/modules/cjs/loader:1383:15)
    at defaultResolveImpl (node:internal/modules/cjs/loader:1025:19)
    at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1030:22)
    at Function._load (node:internal/modules/cjs/loader:1192:37)
    at TracingChannel.traceSync (node:diagnostics_channel:328:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:237:24)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:171:5)
    at node:internal/main/run_main_module:36:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v22.21.1
kittypi@KITTYpi:/usr/local/node/bin $ 

[sdetweil]

@angeliKITTYx i hate this editor on my phone changing the characters

do

node --version

it should report 22.21.1
then

cd ~/MagicMirror
npm run install-mm

[angeliKITTYx]

@sdetweil
it’s booting now! hurray! however, now I’m getting the package lock error when i try to complete the calendarext3 update and none of my events are populating. I have a thread up on someone else’s trouble shooting but I’m out of time this morning. I be back at it this afternoon. thank you again for all your help.

[sdetweil]

@angeliKITTYx awesome. Thanks for the feedback

package-lock? Erase that file then do the update

There is a known bug affecting modules that have functions in their config like ext3. We are discussing ways to distribute these fixes.

[sdetweil]

Did you get the npm run install-mm done after verifying node version was correct?