{
  "context": "Evaluates whether the solution leans on @tailwindcss/node's alias-aware module and stylesheet resolution APIs to load assets from a base directory while reporting dependencies. Checks focus on configuring the package's custom resolver hooks instead of hand-rolled fs logic.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Custom JS resolver",
      "description": "Uses the @tailwindcss/node Resolver signature to translate alias prefixes by passing a customJsResolver into loadModule so aliased specifiers resolve to base-relative absolute paths before import execution.",
      "max_score": 35
    },
    {
      "name": "Default fallback",
      "description": "Leaves loadModule's Enhanced Resolve fallback active for bare or relative specifiers (customJsResolver returns undefined/false) instead of reimplementing resolution, ensuring Node-style paths are produced by the package.",
      "max_score": 20
    },
    {
      "name": "Stylesheet resolver",
      "description": "Resolves CSS specifiers through @tailwindcss/node's loadStylesheet (or compile/compileAst pipeline) with a customCssResolver that maps aliases to absolute paths and returns the package-provided content/path object.",
      "max_score": 30
    },
    {
      "name": "Dependency callbacks",
      "description": "Threads the onDependency callback into both loadModule and loadStylesheet invocations so each resolved absolute path is reported exactly once, matching the package's dependency-tracking behavior.",
      "max_score": 15
    }
  ]
}