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 config helper uses @ice/plugin-icestark to switch between framework and child roles and to configure UMD library naming for child bundles. Scoring looks only at correct plugin invocation and option wiring described in the spec.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Plugin import",
"description": "Uses the @ice/plugin-icestark export (e.g., icestark()) to build the plugin instance inserted into the returned plugins array.",
"max_score": 20
},
{
"name": "Child mode",
"description": "Calls icestark with type set to \"child\" when role is child, ensuring UMD output is enabled for the bundle.",
"max_score": 25
},
{
"name": "Library wiring",
"description": "For string and string[] inputs, forwards the provided library value to the icestark library option so the UMD name(s) match the spec's expectations.",
"max_score": 30
},
{
"name": "Framework mode",
"description": "Calls icestark with type set to \"framework\" for framework role and does not inject library-specific child output settings.",
"max_score": 15
},
{
"name": "Plugins output",
"description": "Places the configured icestark plugin instance inside the returned plugins array exposed by createMicroFrontendConfig.",
"max_score": 10
}
]
}