Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Add Biome for linting and wire up `pnpm lint`

已关闭
#191 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
72/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
github-actions, typescript
领域
ci-cd, tooling

调研方向

Read the root package.json, .editorconfig, existing source under packages//src and packages//tests, website/src, and .github/workflows/ci.yml. Check the existing code style before configuring Biome, then run pnpm lint and review its diff for formatting-only changes. Done means lint passes locally and in CI, with only lint fixes outside the named configuration, package, lockfile, and CI files.

由索引模型根据 Issue 内容生成。

描述

enhancement hacktoberfest help wanted testing

The root package.json has "lint": "pnpm -r lint" (line 12), but no package defines a lint script, so it does nothing. There is no linter or formatter config in the repo, only .editorconfig.

What to do

  • Add Biome as a root dev dependency with a biome.json that matches the current style: 2 spaces, single quotes, semicolons, trailing commas where the code already uses them. Turn on the recommended lint rules.
  • Make pnpm lint run biome check over packages/*/src, packages/*/tests and website/src.
  • Fix what the linter reports. Don't reformat lines that only differ in formatting: set the formatter to match the existing code instead, so the diff stays small.
  • Add a lint step to .github/workflows/ci.yml.

Acceptance criteria

  • pnpm lint passes on dev and runs in CI
  • The PR diff outside biome.json, package.json, the lockfile and CI is lint fixes only, with no formatting-only changes
  • No changeset needed unless a lint fix changes behavior

Want to work on this? Comment below and I'll assign it to you. Please take one issue at a time, branch off dev, and open your PR against dev with Closes #<this issue number>. Setup notes (pnpm, build before test) are in CONTRIBUTING.md.

主要语言
TypeScript
星标
13
派生
7
平均合并
3 小时 41 分钟
30 天内合并 PR
155

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

codercops/chatcops 的其他 Issue

查看 codercops/chatcops 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。