chore(tooling): migrate JS/TS lint and format to the oxc toolchain

Replace ESLint with oxlint and Prettier (for JS/TS) with oxfmt:

- ESLint -> oxlint: add .oxlintrc.json mirroring the previous config
  (ignore patterns, no-unused-vars ^_ exceptions, typescript/unicorn/oxc
  plugins, correctness category); remove eslint, @eslint/js,
  typescript-eslint and eslint.config.mjs.
- Prettier -> oxfmt for JS/TS: add .oxfmtrc.json (migrated from
  .prettierrc.json) and .oxfmtignore. Prettier is kept but scoped to
  JSON/YAML via .prettierignore; SCSS/CSS stay with stylelint. oxfmt uses
  its own --ignore-path so the two formatters never overlap.
- Wire oxlint + oxfmt into husky pre-commit/pre-push and CI build.yml.
- Fix two findings oxlint's default plugins surfaced: unnecessary spread
  over a NodeList (groups.ts) and a dead recursion-only parameter
  (connectSSE in chat/index.ts).
- Update AGENTS.md, docs and CHANGELOG.

Author: thorsten

.github/workflows/build.yml

@@ -85,8 +85,11 @@ jobs:
       - name: Install Node.js dependencies
         run: pnpm install
 
-      - name: Run ESLint check
-        run: pnpm eslint .
+      - name: Run oxfmt format check
+        run: pnpm run oxfmt
+
+      - name: Run oxlint check
+        run: pnpm run oxlint
 
       - name: Run Stylelint check
         run: pnpm run stylelint

.husky/pre-commit

@@ -1 +1 @@
-composer format && composer validate && composer test && pnpm pretty-quick --staged && pnpm run eslint && pnpm run stylelint && pnpm run tsc && pnpm test
+composer format && composer validate && composer test && pnpm pretty-quick --staged && pnpm run oxfmt && pnpm run oxlint && pnpm run stylelint && pnpm run tsc && pnpm test

.husky/pre-push

@@ -1 +1 @@
-composer validate && composer test && pnpm pretty-quick --staged && pnpm run eslint && pnpm run stylelint && pnpm run tsc && pnpm test
+composer validate && composer test && pnpm pretty-quick --staged && pnpm run oxfmt && pnpm run oxlint && pnpm run stylelint && pnpm run tsc && pnpm test

.oxfmtignore

@@ -0,0 +1,5 @@
+# oxfmt formats JavaScript/TypeScript only.
+#
+# Ignore rules live in .oxfmtrc.json ("ignorePatterns"). This file exists so that
+# oxfmt does NOT fall back to reading .prettierignore, which deliberately excludes
+# *.ts/*.js/*.scss — those JS/TS files are formatted by oxfmt, not prettier.

.oxfmtrc.json

@@ -0,0 +1,26 @@
+{
+  "$schema": "./node_modules/oxfmt/configuration_schema.json",
+  "trailingComma": "es5",
+  "tabWidth": 2,
+  "semi": true,
+  "singleQuote": true,
+  "printWidth": 120,
+  "htmlWhitespaceSensitivity": "ignore",
+  "sortPackageJson": false,
+  "ignorePatterns": [
+    ".claude/",
+    "phpmyfaq/admin/assets/js/editor/",
+    "phpmyfaq/src/libs/",
+    "*.php",
+    "*.md",
+    ".github",
+    "composer.json",
+    "composer.lock",
+    "docker-compose.yml",
+    "package.json",
+    "pnpm-lock.yaml",
+    "phpmyfaq/assets/public/",
+    "site/",
+    ".pnpm-store"
+  ]
+}

.oxlintrc.json

@@ -0,0 +1,38 @@
+{
+  "$schema": "./node_modules/oxlint/configuration_schema.json",
+  "plugins": ["typescript", "unicorn", "oxc"],
+  "categories": {
+    "correctness": "error"
+  },
+  "rules": {
+    "no-unused-vars": [
+      "error",
+      {
+        "argsIgnorePattern": "^_",
+        "varsIgnorePattern": "^_",
+        "caughtErrorsIgnorePattern": "^_"
+      }
+    ]
+  },
+  "ignorePatterns": [
+    ".claude/*",
+    "babel.config.cjs",
+    "commitlint.config.cjs",
+    "coverage/*",
+    "html-coverage/*",
+    "node_modules/*",
+    "phpmyfaq/assets/public/*",
+    "phpmyfaq/content/upgrades/*",
+    "phpmyfaq/src/libs/*",
+    "site/*",
+    "volumes/*"
+  ],
+  "overrides": [
+    {
+      "files": ["phpmyfaq/sw.js"],
+      "env": {
+        "serviceworker": true
+      }
+    }
+  ]
+}

.prettierignore

@@ -7,6 +7,18 @@ phpmyfaq/src/libs/
 *.php
 *.md
 
+# JavaScript/TypeScript are formatted by oxfmt (see .oxfmtrc.json)
+*.ts
+*.tsx
+*.js
+*.jsx
+*.mjs
+*.cjs
+
+# SCSS/CSS are handled by stylelint
+*.scss
+*.css
+
 # Ignore code for build
 .github
 composer.json

AGENTS.md

@@ -53,8 +53,10 @@ It is built using HTML5, CSS, TypeScript, and PHP and supports various databases
 - TypeScript code: pnpm test
 - TypeScript code with coverage: pnpm test:coverage
 - TypeScript code in watch mode: pnpm test:watch
-- TypeScript linting: pnpm lint
-- TypeScript code formatting: pnpm lint:fix
+- TypeScript linting: pnpm oxlint
+- TypeScript code formatting check: pnpm oxfmt
+- TypeScript code formatting auto-fix: pnpm oxfmt:fix
+- JSON/YAML formatting: pnpm lint (check) / pnpm lint:fix (auto-fix, prettier)
 - SCSS linting: pnpm stylelint
 - SCSS lint auto-fix: pnpm stylelint:fix
 - TypeScript errors have to be fixed before committing code.

CHANGELOG.md

@@ -40,6 +40,8 @@ This is a log of major user-visible changes in each phpMyFAQ release.
 - migrated codebase using PHP 8.4 language features (Thorsten)
 - migrated routes using PHP 8+ #[Route] attributes (Thorsten)
 - migrated to Vite v8 (Thorsten)
+- migrated from ESLint to oxlint for TypeScript linting (Thorsten)
+- migrated from Prettier to oxfmt for JavaScript/TypeScript formatting (Thorsten)
 - migrated experimental MCP Server to mcp/sdk (Thorsten)
 
 ### phpMyFAQ v4.1.5 - unreleased

docs/development.md

@@ -424,9 +424,9 @@ To run the PHPUnit-based tests, you can use the following command:
 
     $ composer test
 
-To run the ESLint-based checks, you can use the following command:
+To run the oxlint-based checks, you can use the following command:
 
-    $ pnpm eslint .
+    $ pnpm run oxlint
 
 To run the Vitest-based tests, you can use the following command:
 
@@ -482,7 +482,7 @@ phpMyFAQ provides a set of Composer scripts to simplify common development tasks
 The following coding standards are used in phpMyFAQ:
 
 - PHP: [PER Coding Style 3.0](https://www.php-fig.org/per/coding-style/)
-- TypeScript with ESLint recommendations
+- TypeScript with oxlint recommendations
 
 ### 10.6.10 Rebase your Patch