The `punycode` module is deprecated message after Upgrade from 2.33.0 to 2.35.0

[wmx]

Hi everyone,
after my mirror run without any issued for a long time, it still stopped working right now, after I did an upgrade from 2.33.0 to 2.35.0 with the upgrade scripts provided by @sdetweil.

I’m running

Linux 6.12.75+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.75-1+rpt1~bookworm (2026-03-11) aarch64 GNU/Linux

on a Raspi 4.
Previous the upgrade, 2.33.0 was running.
I had to switch from X11 to Wayland in raspi-config to avoid these messages

[3525:0421/204946.469269:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:202] Failed to connect to Wayland display: No such file or directory (2)
[3525:0421/204946.470022:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:281] Failed to initialize Wayland platform
[3525:0421/204946.470333:ERROR:ui/aura/env.cc:246] The platform failed to initialize.  Exiting.

but this error still remains and I do not know how to solve it.

[2026-04-21 20:49:46.375] [ERROR] [unknown] (node:3525) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `electron --trace-deprecation ...` to show where the warning was created) 

After this and the info about the system the script terminates.

Any help is welcome.
Regards

[sdetweil]

Also can you try

export WAYLAND_DISPLAY=wayland-0
npm start

[wmx]

After doing some more research I also updated my 3 additional modules manually.
I thought the update script would also have done this , but it seems it didn’t. The module MMM-homeassistant-sensors wasn’t up to date.

Now it ends with this message

[2026-04-21 22:26:11.173] [LOG]   [app] Starting MagicMirror: v2.35.0
[2026-04-21 22:26:11.199] [LOG]   [utils] Loading config ...
[2026-04-21 22:26:11.212] [INFO]  [utils] Checking config file /home/somename/MagicMirror/config/config.js ...
[2026-04-21 22:26:11.444] [INFO]  [utils] Your configuration file doesn't contain syntax errors :)
[2026-04-21 22:26:11.446] [INFO]  [utils] Checking modules structure configuration ...
[2026-04-21 22:26:11.643] [INFO]  [utils] Your modules structure configuration doesn't contain errors :)
[2026-04-21 22:26:12.799] [LOG]   [MMM-homeassistant-sensors] MMM-homeassistant-sensors helper started...
[2026-04-21 22:26:12.801] [LOG]   [MMM-MQTT] MMM-MQTT: Starting node helper
[2026-04-21 22:26:13.859] [INFO]  [systeminformation]
####  System Information  ####
- SYSTEM:   manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 4 Model B Rev 1.2; virtual: false; MM: v2.35.0
- OS:       platform: linux; distro: Debian GNU/Linux; release: 12; arch: arm64; kernel: 6.12.75+rpt-rpi-v8
- VERSIONS: electron: 41.1.0; used node: 22.21.1; installed node: 22.21.1; npm: 10.9.4; pm2: 6.0.14
- ENV:      XDG_SESSION_TYPE: tty; MM_CONFIG_FILE: undefined
            WAYLAND_DISPLAY:  wayland-1; DISPLAY: :0; ELECTRON_ENABLE_GPU: undefined
- RAM:      total: 3795.80 MB; free: 3025.94 MB; used: 769.87 MB
- OTHERS:   uptime: 75 minutes; timeZone: Europe/Berlin
/home/somename/MagicMirror/node_modules/electron/dist/electron exited with signal SIGTRAP

My mm.sh contains

cd ./MagicMirror
export ELECTRON_DISABLE_GPU=1
export NODE_EXTRA_CA_CERTS=/home/somename/.step/certs/root_ca.crt
DISPLAY=:0 npm start

Is there something else missing?

[sdetweil]

@wmx no. The modules are down level in their package.json dependencies.

[sdetweil]

@wmx the upgrade script only upgrades the base, and does npm
Install for the modules that have dependencies in their package.json.

Upgrading modules is up to the author, and user for the process. Many times deprecated libraries force code changes on update.

[wmx]

@sdetweil ok, understood.
I updated my 3 additional modules but still get

~/MagicMirror/node_modules/electron/dist/electron exited with signal SIGTRAP

If i switch to

DISPLAY=:0 npm run server

it starts and I can see the webpage in a browser, but no screen on my mirror. Here only the graphical desktop.
What else can I do or check?

[sdetweil]

@wmx remember that npm start now does Wayland (from the release notes)
So you have to change it to
npm run start:x11
If still using x

If you used my upgrade script it should have fixed mm.sh if you used pm2 for launch

[sdetweil]

@wmx just reinstalling the old module definition will not fix the old dependency. The author must change the module package

[wmx]

@sdetweil I used your scripts.
After Upgrade I switched to wayfire in raspi-config and rebooted.
But I can try to get back to X11 and try the additional parameter (:x11).
Two of the modules had updates. I updated these (git pull && npm install).

[sdetweil]

@wmx doesn’t sound like system was changed to Wayland. Did you reboot after changing in raspicfg

[wmx]

yes, I did

[sdetweil]

@wmx
Can you run this command string

If Wayland it will output something

ps -ef | grep -v grep | grep -i -e xway -e labwc

[sdetweil]

Also can you try

export WAYLAND_DISPLAY=wayland-0
npm start

[wmx]

@sdetweil
I switched back to X11 in raspi-config, rebooted and added the parameter

DISPLAY=:0 npm run start:x11

That works! :-)
As it is quite after midnight here, I’ll do these tests with wayland tomorrow and respond here.
So far, thank you a lot.