mirror of
https://github.com/danbulant/oxc
synced 2026-05-20 12:48:38 +00:00
17635973b6
Closes #4085 This issue seemed to have been addressed in #3779 , but partially reverted in #3813 ? 🤔 Since I wasn't aware of these changes, I've just checked the current implementation through the review requests in #4611 and refactored as the original author. |
||
|---|---|---|
| .. | ||
| src | ||
| .gitignore | ||
| jsconfig.json | ||
| package.json | ||
| README.md | ||
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@latestfrom 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?
- Some plugins do not provide static rules list
- Easiest way to collect the list is just evaluating config file in JavaScript
- 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