fix(cli): read x-content-length when Content-Length is missing

[Kikobeats]

Summary

• Footer size now falls back to x-content-length when Content-Length is absent (Cloudflare brotli).
• Matches the API header shipped so the browser playground stops printing 0 B.

Test plan

• search footer reports the response size still passes with Content-Length
• New test: mock response with only x-content-length prints that size, not 0 B

Made with Cursor

Summary by CodeRabbit

• Bug Fixes

  • Search result footers now display the correct response size when the standard size information is unavailable.
  • Prevents misleading 0 B sizes from appearing in successful search results.

• Tests

  • Added end-to-end coverage to verify accurate byte counts in search success footers.

[coveralls]

Coverage Report for CI Build 34244871702

Warning

No base build found for commit bc43525 on master.
Coverage changes can't be calculated without a base build.
If a base build is processing, this comment will update automatically when it completes.

Coverage: 77.968%

Details

• Patch coverage: 2 of 2 lines across 1 file are fully covered (100%).

Uncovered Changes

No uncovered changes found.

Coverage Regressions

Requires a base build to compare against. How to fix this →

---

Coverage Stats

Relevant Lines:	4889
Covered Lines:	3815
Line Coverage:	78.03%
Relevant Branches:	830
Covered Branches:	644
Branch Coverage:	77.59%
Branches in Coverage %:	Yes
Coverage Strength:	24.47 hits per line

---

💛 - Coveralls

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 05533870-f489-40ba-a93c-043ae454b3b6

📥 Commits

Reviewing files that changed from the base of the PR and between bc43525 and f6fc41c.

📒 Files selected for processing (2)

• packages/core/bin/print.js
• packages/core/test/cli.mjs

---

📝 Walkthrough

Walkthrough

The CLI footer now uses x-content-length when content-length is unavailable. An end-to-end test verifies the reported byte count and prevents 0 B output.

Changes

CLI response size

Layer / File(s)	Summary
Response size fallback and CLI validation packages/core/bin/print.js, packages/core/test/cli.mjs	printFooter falls back to x-content-length. The CLI test verifies the correct response size and excludes 0 B.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Severity of issue fixed: Low

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/cli-x-content-length

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit f6fc41c. Configure here.}

[cursor]

Test still sends Content-Length

Low Severity

The new test never leaves content-length unset. Node.js adds that header when res.end is given a body, so the footer still reads content-length and the x-content-length fallback is not exercised. The test would pass without the production change.

 

^{Reviewed by Cursor Bugbot for commit f6fc41c. Configure here.}