or run

npx @tessl/cli init
Log in

Version

Files

docs

index.md
tile.json

rubric.jsonevals/scenario-6/

{
  "context": "This criteria evaluates how effectively the engineer uses postcss-modules-extract-imports to manage complex dependency graphs in CSS modules. The focus is on leveraging the package's built-in dependency resolution and topological sorting capabilities rather than implementing graph algorithms from scratch.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "PostCSS integration",
      "description": "Correctly requires and uses postcss-modules-extract-imports as a PostCSS plugin with postcss() to process CSS files",
      "max_score": 15
    },
    {
      "name": "Dependency parsing",
      "description": "Leverages the plugin to automatically parse 'composes' declarations and extract file dependencies, rather than manually parsing CSS syntax with regular expressions or string manipulation",
      "max_score": 20
    },
    {
      "name": "Graph-based ordering",
      "description": "Uses the plugin's dependency graph and topological sort functionality to determine correct file load order based on composition relationships",
      "max_score": 30
    },
    {
      "name": "Circular dependency handling",
      "description": "Relies on the plugin's built-in cycle detection to identify and report circular dependencies as errors, rather than implementing custom cycle detection",
      "max_score": 20
    },
    {
      "name": "Result extraction",
      "description": "Properly extracts the computed import order from the plugin's output (such as from processed :import() rules or dependency graph) and returns it as an array of file paths",
      "max_score": 15
    }
  ]
}