mcpField
E
export-download-debugging

export-download-debugging

github.com/nexu-ioDevelopment104.6k1.8k installsUpdated today
Repository

About export-download-debugging

export-download-debugging is a development skill for diagnosing exports or downloads that produce empty, missing, or unusable files, especially in browser previews, iframe capture, and Electron shells. It verifies the payload before investigating the host's save path and fallback mechanisms.

Key features

  1. 01Separates payload capture from saving
  2. 02Records payload type, MIME, and byte count
  3. 03Checks browser and Electron download evidence
  4. 04Orders save-channel fallback checks
  5. 05Validates export tests and typechecks

Use cases

  1. 01Diagnose exports that produce 0 KB files
  2. 02Investigate save failures in browsers or iframes
  3. 03Inspect Electron download paths and file types
  4. 04Add tests and validation for export fixes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nexu-io/open-design --skill export-download-debugging

After installing, type/export-download-debuggingin Claude Code to confirm it loaded.

Details

From the project README

Export Download Debugging

Use this when an export or download appears to run but produces an empty, missing, or unusable file. It is tuned for browser previews, iframe capture, and Electron shells.

Core rule

Separate capture from save. Prove the export payload has non-zero bytes before debugging the destination path. A 0 KB file often means the native picker or host created the target file, then the write failed or was blocked.

Evidence

  • Record the payload type, MIME type, byte length, object URL or data URL path, and thrown error name/message.
  • Check browser console output and app logs around showSaveFilePicker, createWritable, <a download>, URL.createObjectURL, and URL revocation.
  • In Electron, inspect the will-download path: filename, MIME, file extension, save dialog filters, cancellation, and final file size.
  • Confirm the actual downloaded file size on disk and whether it opens in a normal image viewer.

Fix order

  1. Prepare and validate the export payload first; disable Save until bytes are available.
  2. Prefer the simplest stable save channel for the host. If showSaveFilePicker().createWritable() fails, is sandboxed, or creates empty files, route to <a download> or Electron's download manager instead.
  3. Avoid opening a native picker before the payload is ready. This prevents the host from creating an empty destination file on later write failure.
  4. For PNG fallback, prefer a verified non-empty data URL when blob URLs, revocation timing, CSP, or iframe sandboxing are suspicious.
  5. In Electron, add explicit Save As filters for exported image extensions (.png, .jpg, .jpeg, .webp) so users can choose a real image target.
  6. Keep the UI restrained: format selection, filename/path hint, clear pending and error states, and one primary save action.

Validation

  • Add or update tests for non-empty payload preparation, fallback save behavior, file extension/MIME mapping, and UI disabled/error states.
  • Run focused export tests, then pnpm --filter @open-design/web typecheck.
  • If Electron download handling changed, also run pnpm --filter @open-design/desktop typecheck.
  • Before landing, run pnpm guard, inspect the staged diff for unrelated files, generated artifacts, and accidental secrets, then use the repository's PR quality-gate workflow if the fix is being prepared for review.

Comments

Markdown supported