oxc/tasks/lint_rules
2024-09-08 13:24:58 +08:00
..
src chore: use dprint to format js, json and markdown 2024-09-08 13:24:58 +08:00
.gitignore chore(lint_rules): deprecated eslint no-dupe-args / no-octal / no-with 2024-02-02 17:33:54 +08:00
jsconfig.json feat(tasks): Enable tasks/lint_rules(JS ver) (#2177) 2024-01-26 15:45:05 +08:00
package.json feat(docs): add tracking for plugins "promise" and "vitest" (#4668) 2024-08-05 19:01:44 -04:00
README.md feat(tasks): Enable tasks/lint_rules(JS ver) (#2177) 2024-01-26 15:45:05 +08:00

tasks/lint_rules

Task to update implementation progress for each linter plugin.

Usage:
  $ cmd [--target=<pluginName>]... [--update] [--help]

Options:
  --target, -t: Which plugin to target, multiple allowed
  --update: Update the issue instead of printing to stdout
  --help, -h: Print this help message

Environment variables GITHUB_TOKEN is required when --update is specified.

Design

  • Always install eslint-plugin-XXX@latest from npm
  • Load them through ESLint Node.js API
  • List all their plugin rules(name, deprecated, recommended, docs, etc...)
  • List all our implemented rules(name)
  • Combine these lists and render as markdown
  • Update GitHub issue body

FAQ

  • Why is this task written in Node.js? Why not Rust?
  • Why .cjs?
    • To keep dependencies as simple as possible
    • Some plugins only provide their module as CommonJS
    • So, CommonJS is the only way to go without bundling