openclaw - 💡(How to fix) Fix [Bug]: RangeError: Maximum call stack size exceeded when loading plugins in v2026.4.5 [1 comments, 2 participants]

PS C:\Users\user> openclaw dashboard Exception in PromiseRejectCallback: node:internal/modules/esm/module_job:534 const namespace = this.module.evaluateSync(filename, parentFilename); ^

RangeError: Maximum call stack size exceeded

10:10:54+08:00 [plugins] acpx failed to load from C:\Program Files\nodejs\global\node_modules\openclaw\dist\extensions\acpx\index.js: Error: undefined: Maximum call stack size exceeded C:/Program Files/nodejs/global/node_modules/openclaw/node_modules/@sinclair/typebox/build/cjs/index.js:0:0 10:10:56+08:00 [plugins] alibaba failed to load: Maximum call stack size exceeded 10:10:57+08:00 [plugins] amazon-bedrock failed to load: Maximum call stack size exceeded 10:10:59+08:00 [plugins] anthropic failed to load: Maximum call stack size exceeded 10:11:00+08:00 [plugins] browser failed to load: Maximum call stack size exceeded 10:11:02+08:00 [plugins] deepseek failed to load: Maximum call stack size exceeded ... (all bundled plugins fail with same error)

Workaround: Rolling back to v2026.4.2 resolves the issue. Node.js version: v24.14.0

TL;DR

Rolling back to OpenClaw version 2026.4.2 may resolve the issue of bundled plugins failing to load due to a RangeError: Maximum call stack size exceeded.

Guidance

• The error RangeError: Maximum call stack size exceeded at @sinclair/typebox/build/cjs/index.js suggests a potential issue with recursive function calls or infinite loops, possibly introduced in OpenClaw version 2026.4.5.
• Verify the issue by attempting to load each plugin individually to see if the error persists, which could help isolate the problem to a specific plugin or a common dependency.
• Consider testing with a different version of Node.js, as the issue might be related to the interaction between OpenClaw 2026.4.5 and Node v24.14.0.
• Since rolling back to version 2026.4.2 is mentioned as a workaround, it's likely that the issue is specific to the changes introduced in version 2026.4.5.

Example

No specific code example can be provided without more details on the changes between OpenClaw versions 2026.4.2 and 2026.4.5.

Notes

The exact cause of the RangeError is not specified, and without access to the code changes between versions 2026.4.2 and 2026.4.5, it's challenging to provide a precise fix. The workaround of rolling back to version 2026.4.2 suggests that the issue might be resolved by reverting recent changes.

Recommendation

Apply the workaround by rolling back to OpenClaw version 2026.4.2, as it has been confirmed to resolve the issue of plugins failing to load due to the RangeError.