openclaw - 💡(How to fix) Fix Regression after 2026.4.27: ERR_PACKAGE_PATH_NOT_EXPORTED for @mariozechner/pi-ai/oauth [1 comments, 2 participants]

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './oauth' is not defined by exports in .../@mariozechner/pi-ai/package.json

• lane task error ... ERR_PACKAGE_PATH_NOT_EXPORTED ... ./oauth No package export error; session should continue normally.
• CJS require fails with same error:

TL;DR

The most likely fix is to update the @mariozechner/pi-ai/package.json to include a default or require export for the ./oauth path to ensure compatibility with both ESM and CJS imports.

Guidance

• Verify that the issue is indeed caused by the openclaw upgrade by downgrading to a previous version (e.g., 2026.4.26) and checking if the error persists.
• Check the @mariozechner/pi-ai/package.json file in the installed tree to confirm that it only includes an import export for ./oauth and not a default or require export.
• Consider applying a local hotfix by adding a default or require export for ./oauth in the @mariozechner/pi-ai/package.json file as a temporary workaround.
• If possible, test the ESM import (import('@mariozechner/pi-ai/oauth')) and CJS require (require('@mariozechner/pi-ai/oauth')) in a controlled environment to confirm the import method being used by openclaw.

Example

No code snippet is provided as the issue is related to package configuration and import methods.

Notes

The issue seems to be related to the change in import methods between ESM and CJS, and the @mariozechner/pi-ai package not being properly configured to handle both. The provided temporary workarounds suggest that the issue can be resolved by either downgrading openclaw or updating the package configuration.

Recommendation

Apply the temporary workaround by adding a default or require export for ./oauth in the @mariozechner/pi-ai/package.json file, as this seems to be the most straightforward solution to ensure compatibility with both ESM and CJS imports.