n8n-io/n8n
1
0
Fork 0
mirror of https://github.com/n8n-io/n8n.git synced 2026-10-12 02:19:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore: Migrate backend tooling lint to Oxlint (no-changelog) (#39825)

Browse Source
This commit is contained in:
Matsu
2026-09-29 11:42:22 +00:00
committed by GitHub
parent a45162c5fa
commit 0e5c9aaed6
13 changed files with 134 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
scripts/lint-parity/OXLINT_MIGRATION_BLOCKERS.md
+9 -1
View File
@@ -26,7 +26,7 @@ These rules come from the shared base or backend layers. Resolve these first bec
| P2 | `import/export` | A native rule exists, but it is still in the nursery category. | Run parity samples and enable it after it becomes stable. |
| P3 | `no-octal` | Oxlint has no rule. The parser already rejects relevant octal syntax in module and strict-mode code. | Confirm parser coverage and retire the explicit rule if no supported source form remains. |
## Package-level typed blocker
## Package-level blockers
### `@typescript-eslint/naming-convention`
@@ -41,6 +41,14 @@ Possible approaches:
Audit every package configuration before conversion. Do not copy the full generic naming rule into a new custom implementation.
## Retirement exceptions
### `n8n-node-dev`
Keep `n8n-node-dev` on ESLint. The v3 removal plan makes an Oxlint migration unnecessary.
Reconsider this exception only if the package removal plan changes.
## Frontend package blockers
Oxlint can lint the script section of a Vue SFC, but it does not expose the Vue template AST. An Oxlint-only frontend package would lose the following 59 rules: