or run

npx @tessl/cli init
Log in

Version

Files

tile.json

rubric.jsonevals/scenario-4/

{
  "context": "Evaluates how well the solution leverages Parcel to run production builds for the specified entries, applying output location, public URL, caching, and source map controls while surfacing build failures.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Uses parcel build",
      "description": "Invokes Parcel's production build command (`parcel build` or `new Parcel(...).run()` in production mode) rather than serve/watch, ensuring optimized output.",
      "max_score": 20
    },
    {
      "name": "Dist dir override",
      "description": "Sets the output directory via Parcel options (e.g., `--dist-dir` flag or `defaultTargetOptions.distDir`) based on the provided dist path.",
      "max_score": 20
    },
    {
      "name": "Public URL",
      "description": "Applies the requested base URL using Parcel (`--public-url` flag or `defaultTargetOptions.publicUrl`) so emitted asset references are prefixed correctly.",
      "max_score": 20
    },
    {
      "name": "Source maps toggle",
      "description": "Maps the source map toggle to Parcel options (`--no-source-maps` flag or `defaultTargetOptions.sourceMaps`) to enable or disable maps as requested.",
      "max_score": 15
    },
    {
      "name": "Cache dir",
      "description": "Configures Parcel to use a custom cache directory (`--cache-dir` flag or `cacheDir` option) and relies on that location across builds.",
      "max_score": 15
    },
    {
      "name": "Failure propagation",
      "description": "Surfaces build failures using Parcel diagnostics (non-zero exit, `BuildError`, or `ThrowableDiagnostic`) rather than suppressing errors or continuing with bad entries.",
      "max_score": 10
    }
  ]
}