Steps to reproduce
bun run lint (biome check .) fails on Windows with hundreds of formatter diagnostics. The first reported diff is not about indentation (tabs vs spaces); it shows files using CRLF (\r\n) while Biome’s formatter output uses LF (\n) only. This creates a large Formatter would have printed the following content mismatch across the repo.
Proposed solution: .gitattribute
Because the maintainers run on MacOS/Linux, enforcing LF at the Git layer fits the canonical line ending for the project and avoids per-OS drift:
Add a .gitattributes that normalizes text files to LF in the repo,
Expected behavior
Clean checkout and running bun run lint on Windows, MacOS or Linux should be successful.
Actual behavior
On Windows bun run lint returns numerous linting errors.
overstory version
0.9.3
Bun version
1.3.12
Operating system
Windows 11
Steps to reproduce
bun run lint(biome check .) fails on Windows with hundreds of formatter diagnostics. The first reported diff is not about indentation (tabs vs spaces); it shows files using CRLF (\r\n) while Biome’s formatter output uses LF (\n) only. This creates a large Formatter would have printed the following content mismatch across the repo.Proposed solution: .gitattribute
Because the maintainers run on MacOS/Linux, enforcing LF at the Git layer fits the canonical line ending for the project and avoids per-OS drift:
Add a .gitattributes that normalizes text files to LF in the repo,
Expected behavior
Clean checkout and running
bun run linton Windows, MacOS or Linux should be successful.Actual behavior
On Windows
bun run lintreturns numerous linting errors.overstory version
0.9.3
Bun version
1.3.12
Operating system
Windows 11