openclaw - 💡(How to fix) Fix [Bug]: `/new` command causes ERR_MODULE_NOT_FOUND (grammy) during gateway restart [1 participants]

Error after /new:

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'grammy' imported from C:\Users\19692\AppData\Roaming\npm\node_modules\openclaw\dist\sticker-cache-Cf0p9p0n.js

Gateway logs (repeated):

[gateway-http] stage "slack" threw — skipping: Error: Cannot find module '@slack/web-api' [ws] webchat disconnected code=1001

Notes: grammy IS installed (v1.41.1 CJS). sticker-cache uses ESM import. Only feishu channel enabled. Reproducible every time.

TL;DR

The most likely fix involves ensuring the grammy package is properly resolved during the gateway restart, potentially by adjusting the import method or timing in sticker-cache-*.js.

Guidance

• Verify that the grammy package version (v1.41.1) is compatible with the current Node.js version and the ESM import used in sticker-cache-*.js.
• Check if the issue is related to the difference in module systems (CJS vs ESM) and consider using a consistent module system or a compatibility layer.
• Investigate the possibility of delaying the import of grammy in sticker-cache-*.js until after the gateway has fully restarted, to avoid the ERR_MODULE_NOT_FOUND error.
• Consider adding error handling or a retry mechanism for importing grammy to mitigate the issue and prevent chat history loss.

Example

No specific code example can be provided without modifying the existing codebase, but adjusting the import statement in sticker-cache-*.js to use a dynamic import or a try-catch block might help resolve the issue.

Notes

The issue seems to be related to the timing of the grammy import during the gateway restart. The fact that the error disappears after a page refresh suggests that the import is successful once the gateway has fully restarted. The difference in module systems (CJS vs ESM) might be contributing to the issue.

Recommendation

Apply a workaround to delay or retry the import of grammy in sticker-cache-*.js to avoid the ERR_MODULE_NOT_FOUND error, as the root cause of the issue is not immediately clear and may require further investigation.