openclaw - 💡(How to fix) Fix [Bug]: Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:' [5 comments, 4 participants]

Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:' Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:' Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:' Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'

TL;DR

The issue can be resolved by using a valid file URL scheme, such as file://, for absolute paths on Windows.

Guidance

• Verify that the path being used is a valid absolute path and convert it to a file:// URL if necessary.
• Check the model setup and rendering code to ensure that the path is being constructed correctly.
• Consider using a library or function that can handle path conversions and URL scheme validation.
• Test the fix by rendering the issue with the updated path and verifying that the ERR_UNSUPPORTED_ESM_URL_SCHEME error is no longer thrown.

Example

No code example is provided as the issue does not contain sufficient code context.

Notes

The issue is specific to Windows and the openclaw provider, and the fix may not apply to other operating systems or providers. Additionally, the OpenClaw version is listed as 2026.4.5, but it is unclear if this version is relevant to the issue.

Recommendation

Apply workaround: The issue can be resolved by using a valid file URL scheme, such as file://, for absolute paths on Windows. This workaround is recommended as it directly addresses the error message and is a common solution for this type of issue.