Skip to content

feat: add ESLint and Prettier code quality tools#186

Open
luengnat wants to merge 1 commit intovirattt:mainfrom
luengnat:feature/code-quality-tools
Open

feat: add ESLint and Prettier code quality tools#186
luengnat wants to merge 1 commit intovirattt:mainfrom
luengnat:feature/code-quality-tools

Conversation

@luengnat
Copy link
Copy Markdown

@luengnat luengnat commented Mar 18, 2026

What this PR does

Adds ESLint + Prettier to keep the code clean and consistent.

What's included

  • ESLint with TypeScript rules (catches bugs, enforces style)
  • Prettier for auto-formatting (no more style debates)
  • Pre-commit hooks via Husky (auto-fixes files before you commit)
  • New scripts: bun run lint, bun run format, bun run check
  • Fixed some existing lint issues while I was at it

How it works

Before each commit:

  1. ESLint auto-fixes what it can
  2. Prettier formats everything
  3. If there are remaining errors, commit is blocked

Try it out

bun run lint      # Check for issues
bun run format    # Fix formatting
bun run check     # Run all checks

Why this matters

  • Catches bugs before they reach prod
  • Consistent style across the codebase
  • Less code review time spent on nitpicks
  • Easier for new contributors to follow conventions

Notes

  • Uses Bun (the project's official package manager) instead of npm
  • Added package-lock.json to .gitignore
  • ~37 warnings remain (mostly any types) — can fix in a follow-up
  • CI will run these checks automatically now

🤖 Generated with Claude Code

@luengnat luengnat force-pushed the feature/code-quality-tools branch 5 times, most recently from c885dba to ad149d1 Compare March 18, 2026 05:34
Add comprehensive code quality tooling using Bun:

- ESLint with TypeScript support and recommended rules
- Prettier for consistent code formatting
- Husky + lint-staged for pre-commit hooks
- New scripts: bun run lint, lint:fix, format, format:check, check
- Auto-fixed existing code style issues
- Added CODE_QUALITY.md documentation
- Fixed CI to allow lockfile updates during dependency changes

This ensures consistent code quality and formatting across the project.
@luengnat luengnat force-pushed the feature/code-quality-tools branch from ad149d1 to 6e4767f Compare March 18, 2026 05:38
@swrzalek
Copy link
Copy Markdown
Contributor

What do you think about using oxlint instead?

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.

3 participants