openclaw - 💡(How to fix) Fix [Bug] Slack contract-api.js TypeError: Cannot read properties of undefined (reading 't') [3 comments, 4 participants]

TypeError: Cannot read properties of undefined (reading 't') at Object.get [as legacyConfigRules] (/home/hotplex/.npm-global/lib/node_modules/openclaw/dist/extensions/slack/contract-api.js:1:647) at resolvePluginDoctorContracts (file:///home/hotplex/.npm-global/lib/node_modules/openclaw/dist/config-DMMR1XE_.js:220:52) at listPluginDoctorLegacyConfigRules (file:///home/hotplex/.npm-global/lib/node_modules/openclaw/dist/config-DMMR1XE_.js:233:9) at resolveLegacyConfigForRead (file:///home/hotplex/.npm-global/lib/node_modules/openclaw/dist/config-DMMR1XE_.js:19138:82)

TL;DR

The issue can be resolved by ensuring that the legacyConfigRules import is correctly handled in the contract-api.js file.

Guidance

• Verify that the doctor-contract-Byp5_Sbd.js file exports the legacyConfigRules property correctly.
• Check the contract-api.js file to ensure that the legacyConfigRules import is properly handled, considering the possibility of a default export or a named export.
• Investigate the config-DMMR1XE_.js file to understand why mod.default?.legacyConfigRules or mod.legacyConfigRules is undefined, causing the error when trying to access the t property.
• Consider adding a null check or a default value for legacyConfigRules to prevent the TypeError.

Example

// In contract-api.js, add a null check for legacyConfigRules
import { n as normalizeCompatibilityConfig, t as legacyConfigRules } from "../../doctor-contract-Byp5_Sbd.js";

// ...

if (legacyConfigRules) {
  // Use legacyConfigRules
} else {
  // Handle the case where legacyConfigRules is undefined
}

Notes

The issue seems to be related to the way the legacyConfigRules import is handled in the contract-api.js file. Without more information about the doctor-contract-Byp5_Sbd.js file and its exports, it's difficult to provide a more specific solution.

Recommendation

Apply a workaround by adding null checks or default values for legacyConfigRules to prevent the TypeError, as the root cause of the issue is not entirely clear from the provided information.