{
  "context": "Evaluates whether the solution uses Parcel's dev-server capability to run a hot-reloading SPA with configurable network, HTTPS, and lazy-build behavior. Checks emphasize correct Parcel CLI/API options rather than custom servers or reload logic.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Serve command",
      "description": "Starts the app with Parcel's dev server (`parcel serve` or equivalent Parcel API) targeting the configured entry instead of a custom HTTP server.",
      "max_score": 30
    },
    {
      "name": "HMR handling",
      "description": "Keeps Parcel HMR on by default and depends on Parcel's HMR websocket; uses `--no-hmr` or `hmrOptions: false` when HMR is disabled instead of manual reload loops.",
      "max_score": 20
    },
    {
      "name": "Network options",
      "description": "Maps host/port/open settings to Parcel options (`--host`, `--port`, `--open` or `serveOptions.host/port/open`) and surfaces Parcel's port-in-use error instead of silently choosing a new port.",
      "max_score": 15
    },
    {
      "name": "HTTPS config",
      "description": "Enables HTTPS through Parcel (`--https` plus `--cert`/`--key` or `serveOptions.https` with cert/key paths) rather than wrapping Parcel output with a separate TLS server.",
      "max_score": 15
    },
    {
      "name": "Lazy builds",
      "description": "Implements on-demand builds via Parcel's lazy options (`--lazy`, `--lazy-exclude` or `serveOptions.lazy`) so async routes are deferred while the main entry stays eagerly built.",
      "max_score": 20
    }
  ]
}