multiple error in magic mirror after update from 2.28.0 to 2.36.0

1a2a3a

uhm hi, its been awhile since i updated my MM.

i ran sdetweil upgrade script and these were being upgrade.

doing test run = false
Node currently installed. Checking version number.
Minimum Node version: v22.21.1
Installed Node version: v20.9.0
installing correct version of node and npm, please wait
Check current Node installation ...
Node currently installed. Checking version number.
Minimum Node version: v22.21.1
Installed Node version: v22.21.1
No Node.js upgrade necessary.
Check current NPM installation ...
NPM currently installed. Checking version number.
Minimum npm version: V10.9.4
Installed npm version: V10.9.4
No npm upgrade necessary.

saving custom.css

upgrading from version 2.28.0 to 2.36.0
fetching latest revisions
updating MagicMirror runtime, please wait

> magicmirror@2.36.0 postinstall
> git clean -df fonts vendor modules/default


> magicmirror@2.36.0 prepare
> [ -f node_modules/.bin/husky ] && husky || echo no husky installed.

no husky installed.

i then tried to pm2 start and ran into this error. Ok not exactly error, but the mirror just keep going to blackscreen and nothing then back to wall paper then blackscreen and keep looping this.

(node:1971942) [DEP0044] DeprecationWarning: The `util.isArray` API is deprecated. Please use `Array.isArray()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

then i ran npm start and get the punycode error

[ERROR] [unknown] (node:1970698) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `electron --trace-deprecation ...` to show where the warning was created)
[1970698:0501/224750.044913:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:202] Failed to connect to Wayland display: No such file or directory (2)
[1970698:0501/224750.044978:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:281] Failed to initialize Wayland platform
[1970698:0501/224750.044995:ERROR:ui/aura/env.cc:246] The platform failed to initialize.  Exiting.
/home/hsa/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV

i then read in another thread to do npm run start:x11
this works but the punycode still appear but mirror runs.

feels like theres multiple item for me to fix and im kinda lost.

can some kind soul help me out?

sdetweil

@1a2a3a yeh, fine, but no wayland info there

I see a diff on my mm.sh

if wayland_display is not set, then I set it to
WAYLAND_DISPLAY=wayland-0
but your scripts use wayland-1

SO, lets try this

edit mm.sh again
change this line

  if [ $(ps -ef | grep -v grep | grep -i -e xway -e labwc | wc -l) -ne 1 ]; then

back to

  if [ $(ps -ef | grep -v grep | grep -i -e xway -e labwc | wc -l) -ne 0 ]; then

and change this line

export WAYLAND_DISPLAY=${WAYLAND_DISPLAY:=wayland-0}

to

export WAYLAND_DISPLAY=${WAYLAND_DISPLAY:=wayland-1}

and save mm.sh

then

pm2 stop all
pm2 start MagicMirror

sdetweil

@1a2a3a both of those errors are due to older not updated modules, nothing is broken. We don’t have a way to suppress those messages

Just npm trying to be ‘helpful’

Do this to see which module is forcing the error

NODE_OPTIONS=--trace-deprecation npm run start:xxx

Where xxx is x11 or wayland depending on which window manager your MagicMirror is running on

Then look in the terminal window where you ran the command for the better debug info

1a2a3a

@sdetweil hi there old friend! its been a really long while and i hope all is fine on your end? anyway thanks for the prompt response!

anyway i dont quite get what you mean.

so i ran NODE_OPTIONS=–trace-deprecation npm run start:x11, MM run

when i ran NODE_OPTIONS=–trace-deprecation npm run start:wayland, MM doesnt run…

1a2a3a

@sdetweil my mm.sh is currently -

#!/bin/bash
# This file is still here to keep PM2 working on older installations.
cd ~/MagicMirror
DISPLAY=:0 npm start

should i change it to

#!/bin/bash
# This file is still here to keep PM2 working on older installations.
cd ~/MagicMirror
DISPLAY=:0 npm start:x11

sdetweil

@1a2a3a your Linux/pi system uses a window manager to display the app session window on the screen

In the past it was just x11 (xwindows)
In the last couple years a new thing has appeared , Wayland

We need two different commands to tell which wm is active

If you look in the terminal window where you did the command above, you will see the debug output that will identify the module

Here is mine for punycode

[2026-04-08 19:03:13.384] [INFO]  [helpers] [MMM-HomeAssistantDisplay] [ 'HomeAssistant connected for module_20_MMM-HomeAssistantDisplay' ]
[2026-04-08 19:03:13.391] [ERROR] [unknown] (node:936571) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
    at node:punycode:7:10

So MMM-HomeAssistantDisplay is the module that is causing the message

sdetweil

@1a2a3a no, if it works w npm start, leave it alone

1a2a3a

@sdetweil it didnt show any module error.

[2026-05-01 23:53:38.898] [LOG]   [app] All module helpers loaded.
[2026-05-01 23:53:38.901] [LOG]   [server] Starting server on port 8080 ...
[2026-05-01 23:53:38.911] [ERROR] [unknown] (node:1979206) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `electron --trace-deprecation ...` to show where the warning was created)
[2026-05-01 23:53:39.001] [LOG]   [app] Server started ...

1a2a3a

@sdetweil my pm2 is currently not working at the moment.

i then tried to pm2 start and ran into this error. Ok not exactly error, but the mirror just keep going to blackscreen and nothing then back to wall paper then blackscreen and keep looping this.

(node:1971942) [DEP0044] DeprecationWarning: The `util.isArray` API is deprecated. Please use `Array.isArray()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

sdetweil

@1a2a3a you did this right?

NODE_OPTIONS=--trace-deprecation npm run start:xxx

Replace xxx with x11, the whole line
On your system

That’s 2. — in front of of trace-deprecation

1a2a3a

@sdetweil yes correct

NODE_OPTIONS=–trace-deprecation npm run start:x11

i also manually git pull all the modules and all are up to dates as well.

1a2a3a

@sdetweil how do i fix my pm2 issue?

sdetweil

@1a2a3a need 2 dashes in front of trace

sdetweil

@1a2a3a change the npm start to npm run start:x11

If you had used my upgrade script it would have fixed that

1a2a3a

@sdetweil i did use your upgrade script.

do you mean change it inside mm.sh?

currently its

#!/bin/bash
# This file is still here to keep PM2 working on older installations.
cd ~/MagicMirror
DISPLAY=:0 npm start

change it to

#!/bin/bash
# This file is still here to keep PM2 working on older installations.
cd ~/MagicMirror
DISPLAY=:0 npm run start:x11

correct?

sdetweil

@1a2a3a correct…

in version 2.35 we documented that we changed the default to

npm run start:wayland

for npm start

see package,json, scripts: section for the command options

1a2a3a

@sdetweil same thing

NODE_OPTIONS=--trace-deprecation npm run start:x11

[2026-05-02 00:31:24.574] [LOG]   [node_helper] Module helper loaded: MMM-CalendarExt3
[2026-05-02 00:31:24.574] [LOG]   [app] All module helpers loaded.
[2026-05-02 00:31:24.592] [LOG]   [server] Starting server on port 8080 ...
[2026-05-02 00:31:24.602] [ERROR] [unknown] (node:1985687) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
    at node:punycode:7:10
    at BuiltinModule.compileForInternalLoader (node:internal/bootstrap/realm:398:7)
    at BuiltinModule.compileForPublicLoader (node:internal/bootstrap/realm:337:10)
    at loadBuiltinModule (node:internal/modules/helpers:126:7)
    at loadBuiltinWithHooks (node:internal/modules/cjs/loader:1229:15)
    at Module._load (node:internal/modules/cjs/loader:1320:48)
    at c._load (node:electron/js2c/node_init:2:18060)
    at wrapModuleLoad (node:internal/modules/cjs/loader:262:19)
    at Module.require (node:internal/modules/cjs/loader:1583:12)
    at require (node:internal/modules/helpers:153:16)
[2026-05-02 00:31:24.702] [LOG]   [app] Server started ...
[2026-05-02 00:31:24.703] [LOG]   [node_helper] Connectin```
code_text

1a2a3a

@sdetweil i have change my mm.sh to

#!/bin/bash
# This file is still here to keep PM2 working on older installations.
cd ~/MagicMirror
DISPLAY=:0 npm run start:x11

but when i do pm2 start MagicMirror, it doesnt start still.

sdetweil

@1a2a3a SO much fun

do this and give me the output

grep "module:" ~/MagicMirror/config/config.js | sort | uniq

and I’ll look thru them

1a2a3a

@sdetweil here you go

[hsa@HSA:~ $ grep "module:" ~/MagicMirror/config/config.js
                        module: "alert",
                        module: "updatenotification",
                        module: "clock",
        module: "MMM-Jast",
  module: 'MMM-GoogleDocs-Notes',
                        module: "newsfeed",
                module: "MMM-NewsAPI",
  module: "MMM-MyScoreboard",
  module: "MMM-SoccerLiveScore",
//  module: "MMM-GooglePhotos",
// module: "MMM-ImagesPhotos",
//   module: "MMM-Wallpaper",
//    module: 'MMM-BackgroundSlideshow',
  module: "MMM-OneDrive",
  module: "MMM-CalendarExt3Agenda",
                        module: "calendar",
                         module: "MMM-CalendarExt3",
                        module: "calendar",](link url)

sdetweil

@1a2a3a ok, I didn’t find it the easy way

lets try the easier way

find ~/MagicMirror/modules -type d | grep punycode | sort

each module listed has it as a dependency either directly or indirectly
on my system (with a lot of modules installed, but most not used)

/home/sam/MagicMirror/modules/Hello-Lucy/node_modules/punycode
/home/sam/MagicMirror/modules/MMM-BMI/node_modules/punycode
/home/sam/MagicMirror/modules/MMM-CalvinAndHobbes/node_modules/punycode
/home/sam/MagicMirror/modules/MMM-FinParcel/node_modules/punycode
/home/sam/MagicMirror/modules/MMM-GoogleCalendar/node_modules/punycode
/home/sam/MagicMirror/modules/MMM-HomeAssistantDisplay/node_modules/punycode
/home/sam/MagicMirror/modules/MMM-homeassistant-sensors/node_modules/punycode
/home/sam/MagicMirror/modules/MMM-json/node_modules/npm/node_modules/punycode
/home/sam/MagicMirror/modules/MMM-json/node_modules/npm/node_modules/uri-js/node_modules/punycode
/home/sam/MagicMirror/modules/MMM-json/node_modules/punycode
/home/sam/MagicMirror/modules/MMM-Lottery/node_modules/punycode
/home/sam/MagicMirror/modules/MMM-MARS/node_modules/punycode
/home/sam/MagicMirror/modules/MMM-NOAA3/node_modules/punycode
/home/sam/MagicMirror/modules/MMM-OnSpotify/node_modules/punycode
/home/sam/MagicMirror/modules/MMM-Reddit/node_modules/psl/node_modules/punycode
/home/sam/MagicMirror/modules/MMM-Reddit/node_modules/request/node_modules/punycode
/home/sam/MagicMirror/modules/MMM-Reddit/node_modules/uri-js/node_modules/punycode
/home/sam/MagicMirror/modules/MMM-SmartWebDisplay/node_modules/punycode
/home/sam/MagicMirror/modules/MMM-Strava/node_modules/punycode
/home/sam/MagicMirror/modules/MMM-Surf/node_modules/punycode
/home/sam/MagicMirror/modules/MMM-Todoist/node_modules/punycode

because its not listed in one of the modules directly, its a dependency of a dependency