docs
evals
scenario-1
scenario-10
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
{
"context": "Evaluates how well the solution drives Parcel 2's incremental bundling via the watch command, wiring options for output and watch scope, reporting rebuild events, and shutting down cleanly. Checks that rebuild feedback and shutdown behavior rely on Parcel APIs rather than ad hoc tooling.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Watch invocation",
"description": "Starts Parcel in watch mode (`parcel watch` CLI or `new Parcel(...).watch()` from @parcel/core) with the provided entry files instead of a single `build`, awaiting the first build before returning.",
"max_score": 30
},
{
"name": "Output dir",
"description": "Configures the bundle output location through Parcel (`--dist-dir` flag or `defaultTargetOptions.distDir`) so initial artifacts land in the caller-specified directory.",
"max_score": 15
},
{
"name": "Scope & ignores",
"description": "Limits rebuild triggers using Parcel watch options such as `--watch-dir`/`watchDir` and `--watch-ignore`/`watch.ignore`, rather than ad-hoc filtering after rebuilds.",
"max_score": 20
},
{
"name": "Rebuild events",
"description": "Subscribes to Parcel watch events (`buildSuccess`/`buildFailure`) and surfaces `event.changedAssets`, `event.buildTime`, or `event.diagnostics` to status callbacks so callers see what changed and how long rebuilds took.",
"max_score": 20
},
{
"name": "Graceful stop",
"description": "Stops the watcher via Parcel APIs (e.g., `subscription.unsubscribe()` or `watch.stop()`) in response to stdin quit signals and ensures workers are disposed before exit.",
"max_score": 15
}
]
}