docs
evals
scenario-1
scenario-10
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
{
"context": "Evaluates whether the solution wires Parcel's lazy async bundle support correctly. Checks that deferred builds, scoped include globs, and eager exceptions are implemented while running a dev server.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Lazy enabled",
"description": "Parcel serve/watch is invoked with the lazy async bundle mode turned on (e.g., Parcel options or CLI --lazy) so async chunks are deferred by default.",
"max_score": 25
},
{
"name": "Include globs",
"description": "Provided lazy include globs are forwarded to Parcel (e.g., --lazy <glob> or Parcel options.lazy) to scope which async bundles are deferred instead of applying lazy mode globally.",
"max_score": 20
},
{
"name": "Exclude globs",
"description": "Eager exceptions are implemented by passing exclusion globs to Parcel (e.g., --lazy-exclude or options.lazyExcludes) so matching async bundles build immediately even when lazy mode is on.",
"max_score": 20
},
{
"name": "Deferred builds",
"description": "Startup flow avoids prebuilding lazy-targeted async bundles and triggers their build only after the first request, relying on Parcel's lazy compilation behavior rather than manual file toggles.",
"max_score": 20
},
{
"name": "Parcel dev server",
"description": "Server lifecycle uses Parcel's serve/watch entry points (CLI or @parcel/core) to host entries, returning the served URL and a stop/dispose hook that correctly tears down the Parcel instance.",
"max_score": 15
}
]
}