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 the solution uses @ice/plugin-icestark to configure a child micro-frontend build with custom UMD library naming. Focuses on deriving the library option from env or package defaults, applying child-mode webpack hooks, and exposing the value via window.ICESTARK.library.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Child plugin mode",
"description": "Registers the icestark plugin with type \"child\" so child-specific webpack config and runtime hooks are enabled.",
"max_score": 25
},
{
"name": "Library option wiring",
"description": "Derives the icestark library option from MICRO_LIB_LABELS (supports comma-split arrays) and falls back to the package name or microApp default when unset.",
"max_score": 25
},
{
"name": "Global export",
"description": "Relies on the plugin-provided entry code to set window.ICESTARK.library to the configured library value(s) instead of leaving it undefined.",
"max_score": 20
},
{
"name": "UMD output",
"description": "Ensures the icestark child plugin sets webpack output.library to the chosen name(s) and output.libraryTarget to \"umd\" for host consumption.",
"max_score": 30
}
]
}