Skip to content

chore: replace eslint with oxlint/oxfmt and add CI workflow - #23

Closed
tknkaa wants to merge 6 commits into
mainfrom
setup-oxlint-oxfmt
Closed

chore: replace eslint with oxlint/oxfmt and add CI workflow#23
tknkaa wants to merge 6 commits into
mainfrom
setup-oxlint-oxfmt

Conversation

@tknkaa

@tknkaa tknkaa commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

Swap eslint/eslint-config-next for oxlint and oxfmt, and add a
GitHub Actions workflow that runs lint, format:check, and typecheck
on push/PR.


Stack created with GitHub Stacks CLIGive Feedback 💬

Swap eslint/eslint-config-next for oxlint and oxfmt, and add a
GitHub Actions workflow that runs lint, format:check, and typecheck
on push/PR.
@tknkaa
tknkaa marked this pull request as ready for review August 14, 2026 10:51
@tknkaa
tknkaa requested a review from Tatsu723 August 14, 2026 11:04
@na-trium-144

na-trium-144 commented Aug 14, 2026

Copy link
Copy Markdown

ciではtscよりもビルドをチェックすべきなのでは?(と思ったけどデプロイとプレビュー入れたらそのときにビルドすることになるからgithub actionでは不要か)
その場合、nextjsではビルド時にtscのエラーは出るので、tsc単体のチェックは不要だったと思います
そうしない場合(別でtscだけしたい場合)、ビルド時の自動tscをオフにするとビルドが早くなると思います
https://nextjs.org/docs/app/api-reference/config/next-config-js/typescript

(oxlint導入に関しては個人的には別にeslint+nextjs公式のプラグインのままでも無難で良いのではという気持ちはあります)

tknkaa added 3 commits August 14, 2026 20:51
next build already surfaces tsc errors; CI doesn't build separately
(deploy pipeline does), so keeping a redundant typecheck job here
just slows CI down for no extra safety.
Switch back from oxlint to eslint with the official eslint-config-next
preset per review feedback, since it catches Next.js/React rules
(e.g. react-hooks/set-state-in-effect) that weren't covered under
oxlint's default config. oxfmt stays for formatting.
@tknkaa

tknkaa commented Aug 15, 2026

Copy link
Copy Markdown
Contributor Author

#25 に全変更(setup + format + fix)を統合したのでこちらはクローズします。

@tknkaa tknkaa closed this Aug 15, 2026
@tknkaa
tknkaa deleted the setup-oxlint-oxfmt branch August 15, 2026 11:50
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