openclaw - ✅(Solved) Fix export-html template.html malformed by formatter causing export failure [5 pull requests, 1 comments, 1 participants]

openclaw2026-03-12 03:00:21

ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

GitHub issue URL

Helpful · Quick feedback

GitHub stats

openclaw/openclaw#43620•Fetched 2026-04-08 00:16:44

View on GitHub

Comments

Participants

Timeline

Reactions

Author

yunlzhang

Participants

yunlzhang

Timeline (top)

referenced ×7cross-referenced ×5

Error Message

Uncaught ReferenceError: MARKED_JS is not defined Uncaught ReferenceError: HIGHLIGHT_JS is not defined Uncaught ReferenceError: JS is not defined

Root Cause

Placeholders in dist/export-html/template.html are incorrectly split into multi-line format by code formatters (e.g., prettier):

Expected format:

<script>{{MARKED_JS}}</script>

Actual format:

<script>
 {
 {
 MARKED_JS;
 }
 }
</script>

The code uses .replace("{{MARKED_JS}}", markedJs) for substitution, but since the placeholder is split across lines, the replacement fails, resulting in undefined JavaScript variables in the generated HTML.

Code Example

Uncaught ReferenceError: MARKED_JS is not defined
Uncaught ReferenceError: HIGHLIGHT_JS is not defined
Uncaught ReferenceError: JS is not defined

---

<script>{{MARKED_JS}}</script>

---

<script>
 {
 {
 MARKED_JS;
 }
 }
</script>

RAW_BUFFERClick to expand / collapse

Bug Description

Exported session HTML files fail to open. Browser console shows:

Uncaught ReferenceError: MARKED_JS is not defined
Uncaught ReferenceError: HIGHLIGHT_JS is not defined
Uncaught ReferenceError: JS is not defined

Root Cause

Placeholders in dist/export-html/template.html are incorrectly split into multi-line format by code formatters (e.g., prettier):

Expected format:

<script>{{MARKED_JS}}</script>

Actual format:

<script>
 {
 {
 MARKED_JS;
 }
 }
</script>

Affected Placeholders

{{MARKED_JS}}
{{HIGHLIGHT_JS}}
{{JS}}

Suggested Fixes

Protect placeholders with HTML comments to prevent formatting
Add formatting ignore rules for .html files in the build process
Use regex replacement in code to tolerate whitespace

Workaround

Manually edit dist/export-html/template.html and restore single-line placeholder format.

Environment

OpenClaw version: latest (2026-03-11)
Node: v22.12.0
OS: macOS (arm64)

extent analysis

Fix Plan

To fix the issue, we will use regex replacement in code to tolerate whitespace. We will modify the replacement code to use a regex pattern that matches the placeholders across multiple lines.

Code Changes

// Before
const html = template.replace("{{MARKED_JS}}", markedJs);
const html = template.replace("{{HIGHLIGHT_JS}}", highlightJs);
const html = template.replace("{{JS}}", js);

// After
const html = template.replace(/{{\s*MARKED_JS\s*}}/g, markedJs);
const html = html.replace(/{{\s*HIGHLIGHT_JS\s*}}/g, highlightJs);
const html = html.replace(/{{\s*JS\s*}}/g, js);

Verification

After making the code changes, verify that the exported session HTML files open correctly in the browser and that the browser console does not show any Uncaught ReferenceError messages.

Extra Tips

Consider adding formatting ignore rules for .html files in the build process to prevent this issue in the future.
Use a code formatter that can be configured to ignore certain files or patterns to prevent unwanted formatting changes.

Vote matrix · Quick signals

Works

Did the solution work? Tap to confirm.

Easy Fix

Was it a quick fix?

Time Saver

Did it save you time?

Blocking

Was it severely blocking?

Common Issue

Are others likely hitting this too?

Flaky / Intermittent

Is it intermittent?

Verified / Reproducible

Can you reproduce it reliably?

#api #ssr #installation #tensor shape #autograd error #cache error #pipeline error #runtime error #dependency conflict #environment setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

openclaw - ✅(Solved) Fix export-html template.html malformed by formatter causing export failure [5 pull requests, 1 comments, 1 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Root Cause

Fix Action

Workaround

PR fix notes

PR #43634: fix: restore export-html template placeholders and prevent reformatting

Description (problem / solution / changelog)

Changed files

PR #43635: # fix(export-html): Restore template placeholders to fix session HTML export failure

Description (problem / solution / changelog)

fix(export-html): Restore template placeholders to fix session HTML export failure

Summary

Use Cases

Behavior Changes

Existing Functionality Check

What Changed

Tests

Manual Testing

Files Changed

Checklist

Changed files

PR #43885: fix: restore final response delivery when Telegram reasoning mode is "on"

Description (problem / solution / changelog)

Summary

Behavior Changes

Existing Functionality Check

What Changed

Tests

Files Changed

Checklist

Changed files

PR #47288: fix: restore export-html template placeholders to single-line format (closes #43620)

Description (problem / solution / changelog)

Summary

Change Type

Scope

Linked Issue/PR

User-visible / Behavior Changes

Security Impact

Repro + Verification

Steps

Expected

Actual (before fix)

Evidence

Human Verification

Review Conversations

Compatibility / Migration

Failure Recovery

Risks and Mitigations

Changed files

PR #47778: fix: restore export-html template placeholders to single-line format (closes #43620)

Description (problem / solution / changelog)

Summary

Change Type

Scope

Linked Issue/PR

User-visible / Behavior Changes

Security Impact

Repro + Verification

Steps

Expected

Actual (before fix)

Evidence

Human Verification

Review Conversations

Compatibility / Migration

Failure Recovery

Risks and Mitigations

Changed files

Code Example

Bug Description

Root Cause

Affected Placeholders

Suggested Fixes

Workaround

Environment

extent analysis