Fix formatting of bun build command in deploy.md

[Revaycolizer]

Fix: Add missing line continuation in bun build command

The original multi-line bun build script was missing a line continuation () after the --target bun flag. Due to this, the next line (--outfile server) was not treated as being part of the same command, and Bun interpreted it incorrectly.

This patch fixes the issue by adding the missing backslash so that all flags and arguments are correctly sent to bun build.

Why it's important:

Prevents build-time errors due to incorrectly formatted CLI input

Makes the command easier to read and maintain

Matches conventional shell scripting standards

Verified that the build now works with all flags enabled:

Compiled output

Minified whitespace and syntax

Targeting Bun runtime

Custom output file

Summary by CodeRabbit

• Documentation
  • Minor formatting update to deployment documentation for improved readability.

[coderabbitai]

Walkthrough

A documentation file receives a minor formatting update: a backslash continuation character is added to a multi-line Bun build command to improve readability. No semantic changes or modifications to command behavior.

Changes

Cohort / File(s)	Summary
Documentation formatting docs/patterns/deploy.md	Added backslash continuation character to multi-line Bun build command for proper line continuation syntax

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A tiny backslash joins the line,
The Bun command now reads just fine,
A dash of syntax, clean and bright,
Makes documentation pixel-perfect right! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "Fix formatting of bun build command in deploy.md" directly and accurately describes the main change in the changeset. The title specifically identifies what is being fixed (the formatting of a bun build command), what file is affected (deploy.md), and the nature of the change (adding a missing line continuation backslash). The title is concise, clear, and specific enough that a teammate scanning the commit history would immediately understand the primary purpose of this change without needing to review the full diff.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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 and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

docs/patterns/deploy.md (1)

66-66: Minor: Hard tabs flagged by linter.

The static analysis tool flagged hard tabs at line 66 (MD010, no-hard-tabs). While this is a pre-existing pattern throughout all bash code blocks in the file and your change maintains consistency with the existing style, you may want to consider whether to standardize on spaces across all code blocks to comply with markdownlint rules.

This is a chill-level observation; the current change is acceptable as-is.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7f08c7c and 3f1b557.

📒 Files selected for processing (1)

• docs/patterns/deploy.md (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.18.1)

docs/patterns/deploy.md

66-66: Hard tabs
Column: 1

(MD010, no-hard-tabs)

🔇 Additional comments (1)

docs/patterns/deploy.md (1)

62-69: ✅ Backslash continuation correctly added.

The missing line continuation backslash has been properly added to line 66 after --target bun, restoring proper shell command parsing for the multi-line bun build invocation. The change correctly ensures all flags and arguments are passed to a single command instead of being split across separate commands.