fix(build): correct nodeBuildConfig comment to match tsdown ESM default

mmyzwl · mmyzwl · commit fe909a4dc02f · 2026-06-27T01:58:17.000+08:00
The previous comment claimed tsdown defaults omitted format to CJS for .ts entries, but tsdown 0.22.1 resolves toArray(format, 'esm') — ESM is the default. Update the comment to accurately describe the explicit format pin as a build-contract consistency and defense-in-depth measure. Part of #91539
diff --git a/tsdown.config.ts b/tsdown.config.ts
@@ -137,11 +137,11 @@ function nodeBuildConfig(config: UserConfig): UserConfig {
   return {
     ...config,
     env,
-    // Explicit ESM output for the "type": "module" package. Without this,
-    // tsdown defaults to CJS for .ts entries, producing module.exports
-    // output that Node.js ignores when loaded via dynamic import() in an
-    // ESM context — causing bundled-plugin public artifact files (e.g.
-    // document-extractor.js) to silently export nothing.
+    // Explicit ESM format pin for OpenClaw's "type": "module" package.
+    // tsdown 0.22.1 already defaults to ESM for omitted format, so this
+    // is an explicit build-contract pin for consistency with the existing
+    // nodeWorkspacePackageBuildConfig() and defense-in-depth against any
+    // future tsdown default change.
     format: "esm",
     fixedExtension: false,
     platform: "node",
