[DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.

[Stefan-Verwey]

I upgraded to the latest Node-Red version today and got this error message in the Logs....

start
node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js
5 Jan 19:05:21 - [info]
Welcome to Node-RED
===================
5 Jan 19:05:21 - [info] Node-RED version: v4.0.8
5 Jan 19:05:21 - [info] Node.js version: v22.11.0
5 Jan 19:05:21 - [info] Linux 6.6.62-haos-raspi arm64 LE
5 Jan 19:05:22 - [info] Loading palette nodes
5 Jan 19:05:24 - [info] Node-RED Contrib Theme Collection version: v4.0.11
5 Jan 19:05:30 - [info] apple-findme-reloaded version: 0.1.8
5 Jan 19:05:38 - [info] Dashboard version 2.30.0 started at /endpoint/ui
(node:386) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use node --trace-deprecation ... to show where the warning was created)
child error: Error: spawn python3 ENOENT**
5 Jan 19:05:45 - [red] Uncaught Exception:
5 Jan 19:05:45 - [error] ReferenceError: require is not defined
at file:///config/node_modules/safefs/es6/lib/safefs.js:2:16
at ModuleJobSync.runSync (node:internal/modules/esm/module_job:366:35)
at ModuleLoader.importSyncForRequire (node:internal/modules/esm/loader:325:47)
at loadESMFromCJS (node:internal/modules/cjs/loader:1381:24)
at Module._compile (node:internal/modules/cjs/loader:1503:5)
at Object..js (node:internal/modules/cjs/loader:1689:10)
at Module.load (node:internal/modules/cjs/loader:1318:32)
at Function._load (node:internal/modules/cjs/loader:1128:12)
at TracingChannel.traceSync (node:diagnostics_channel:315:14)
at wrapModuleLoad (node:internal/modules/cjs/loader:218:24)
at Module.require (node:internal/modules/cjs/loader:1340:12)
at require (node:internal/modules/helpers:141:16)
at Object. (/config/node_modules/safefs/es6guardian.js:11:20)
at Module._compile (node:internal/modules/cjs/loader:1546:14)
at Object..js (node:internal/modules/cjs/loader:1689:10)
at Module.load (node:internal/modules/cjs/loader:1318:32)
at Function._load (node:internal/modules/cjs/loader:1128:12)
at TracingChannel.traceSync (node:diagnostics_channel:315:14)
at wrapModuleLoad (node:internal/modules/cjs/loader:218:24)
at Module.require (node:internal/modules/cjs/loader:1340:12)
at require (node:internal/modules/helpers:141:16)
at Object. (/config/node_modules/scandirectory/out/lib/scandirectory.js:9:12)
[19:05:45] INFO: Service Node-RED exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
[19:05:45] INFO: Service NGINX exited with code 256 (by signal 15)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service nodered: stopping
s6-rc: info: service init-nginx successfully stopped
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

---

Add-on: Node-RED
Flow-based programming for the Internet of Things

Add-on version: 19.0.0
You are running the latest version of this add-on.
System: Home Assistant OS 14.1 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2025.1.0
Home Assistant Supervisor: 2024.12.3

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
s6-rc: info: service init-nginx successfully started
up to date, audited 1243 packages in 53s
100 packages are looking for funding
run npm fund for details
98 vulnerabilities (6 low, 40 moderate, 46 high, 6 critical)
To address issues that do not require attention, run:
npm audit fix
To address all issues possible (including breaking changes), run:
npm audit fix --force
Some issues need review, and may require choosing
a different dependency.
Run npm audit for details.
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
s6-rc: info: service nodered successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started

[sinclairpaul]

Based on at Object. (/config/node_modules/scandirectory/out/lib/scandirectory.js:9:12) in your logs it's likely to do with one of the palettes you have installed and the NodeJS version upgrade.

As these are custom installs, it's challenging to know which palette is causing the issue, from the description do you have anything that does file scans?

You can always set the Safe Mode option and enable as needed https://github.com/hassio-addons/addon-node-red/blob/main/node-red/DOCS.md#option-safe_mode

[Stefan-Verwey]

Hi PaulNope, I am not aware of anything doing file scans. How do one run the Node-Red in Safe Mode?Also, I do not know what you reference or mean with one of the Palettes that I had installed?RegardsStefanSent from my iPhoneOn 6 Jan 2025, at 00:34, Paul Sinclair ***@***.***> wrote: Based on at Object. (/config/node_modules/scandirectory/out/lib/scandirectory.js:9:12) in your logs it's likely to do with one of the palettes you have installed and the NodeJS version upgrade. As these are custom installs, it's challenging to know which palette is causing the issue, from the description do you have anything that does file scans? You can always set the Safe Mode option and enable as needed https://github.com/hassio-addons/addon-node-red/blob/main/node-red/DOCS.md#option-safe_mode —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[bmorgan99]

I had the same error after the same node-red update. I re-installed node-red (maybe not necessary?) and installed the needed palette nodes one at a time. Turns out my problem was node-red-contrib-wfwatch. Fortunately, it was in a flow I use for testing and not even enabled.

[Stefan-Verwey]

Hello Mr MorganThanks for the update What is the Palettes you refer to, sub modules of NodeRed?RegardsStefanOn 6 Jan 2025, at 15:29, bmorgan99 ***@***.***> wrote: I had the same error after the same node-red update. I re-installed node-red (maybe not necessary?) and installed the needed palette nodes one at a time. Turns out my problem was node-red-contrib-wfwatch. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>