{
  "context": "Evaluates how well the solution wires eslint-plugin-import-x's Node resolver factory into a helper that resolves imports for linting. Focus is on forwarding options for extensions, conditions, and module search paths while keeping the factory's builtin handling intact.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Factory usage",
      "description": "Uses eslint-plugin-import-x's exported createNodeResolver to build the resolver (no custom resolver implementation), preserving the factory-provided interfaceVersion 3, name, and resolve behavior.",
      "max_score": 25
    },
    {
      "name": "Builtin handling",
      "description": "Leverages createNodeResolver's builtin/data: URL handling so builtins resolve with found=true and path=null without manual filesystem checks.",
      "max_score": 15
    },
    {
      "name": "Extension options",
      "description": "Passes the user-supplied extensions array directly into createNodeResolver so extensions like ['.ts'] allow resolving ./utils/helpers.ts from fixtures/app/src/index.ts.",
      "max_score": 20
    },
    {
      "name": "Condition ordering",
      "description": "Forwards the conditionNames option to createNodeResolver so ['require', 'default'] prioritizes the require export and resolves pkg-conditional to fixtures/vendor/pkg-conditional/cjs.js.",
      "max_score": 20
    },
    {
      "name": "Module directories",
      "description": "Supplies modules/moduleDirectory search paths to createNodeResolver so bare specifiers located under fixtures/vendor (e.g., vendor-tool) resolve to their expected files.",
      "max_score": 20
    }
  ]
}