ESLint plugin providing comprehensive linting rules for ES2015+ import/export syntax with static analysis and module system enforcement.
80
Pending
Does it follow best practices?
Impact
80%
0.96xAverage score across 10 eval scenarios
Pending
The risk profile of this skill
{
"context": "Evaluates how the solution uses eslint-plugin-import-x to enforce webpack chunk name comments on dynamic imports and return structured lint results for the provided API. Scoring prioritizes correct rule configuration, regex enforcement, and surfacing rule findings in the reported output.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Rule enabled",
"description": "Configures ESLint with the import-x plugin and activates the `import-x/dynamic-import-chunkname` rule for the code being checked.",
"max_score": 25
},
{
"name": "Format regex",
"description": "Sets the rule's `webpackChunknameFormat` option to a kebab-case pattern such as `^[a-z]+(?:-[a-z0-9]+)*$` so valid chunk names like \"feature-settings\" pass and malformed names fail.",
"max_score": 25
},
{
"name": "Missing comment catch",
"description": "Relies on the rule's `leadingComment` violation to flag dynamic imports that omit a `webpackChunkName` comment, producing an error message tied to the import target.",
"max_score": 20
},
{
"name": "Import functions",
"description": "Keeps the rule checking the actual dynamic import call sites (defaulting to `import()`), configuring the `importFunctions` option when needed so all dynamic imports in scope are validated for chunk names.",
"max_score": 15
},
{
"name": "Result reporting",
"description": "Uses ESLint results from the `dynamic-import-chunkname` rule to populate the returned report, preserving line/column data and mentioning the offending specifier or chunk name in messages as the spec requires.",
"max_score": 15
}
]
}docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10