Skip to content

Check formatting and lint with bun fmt and bun lint (canary) - #28

Merged
lperezmo merged 2 commits into
mainfrom
build/bun-fmt-lint
Oct 22, 2026
Merged

lperezmo merged 2 commits into
mainfrom
build/bun-fmt-lint

Conversation

@lperezmo

Copy link
Copy Markdown
Owner

Before: nothing checked formatting or lint.

After: a format-and-lint job in the existing test workflow runs bun fmt --check . and bun lint --max-warnings 0 on bun canary, and the code is formatted to match.

bun fmt and bun lint only ship in canary builds so far, so the job installs canary. Same setup as outlook-mcp, memory-browser and drawlab.

How:

  • style: format with bun fmt is a formatting-only commit. bunfig.toml sets the formatter to the style the code already had (no semicolons, single quotes, printWidth 120), which keeps the diff small, and turns on eqeqeq (smart).
  • packs/ and tools/packs/ come from the Python pack builder, which has its own ruff checks, so .prettierignore leaves them alone.
  • A test path 'C:\work\notes.md' held a newline (\n) and a bare w; it is now escaped as 'C:\\work\\notes.md' and the test still passes.

Verified locally with bun 1.4.4-canary.1 and Claude Code 2.1.307: fmt check clean, lint 0 problems, claude plugin validate passes. claude plugin test .: 103 pass.

The plugin directory's own validator (which once refused .gitattributes) can't be run from here, so it hasn't checked the new bunfig.toml and .prettierignore at the repo root.


Generated by Claude Code

One-time pass with bun fmt, configured in bunfig.toml to match the existing
style (no semicolons, single quotes, printWidth 120).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Adds a job that runs bun fmt --check and bun lint --max-warnings 0 on bun
canary (neither is in a stable release yet), turns on eqeqeq (smart), and
clears the warnings the linter found.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@lperezmo
lperezmo merged commit 428a8e5 into main Oct 22, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants