{"version":"2.1.248","anchor":"lazy-modules-now-loaded-through-a-direct-chunk-require","canonical_anchor":"lazy-modules-now-loaded-through-a-direct-chunk-require","heading":"Lazy modules now loaded through a direct chunk require","tier":"internal","area":"Startup","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/lazy-modules-now-loaded-through-a-direct-chunk-require","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Lazy modules now loaded through a direct chunk require\n\nTwo modules now load through direct chunk requires instead of the bundler shim.\n\n**What**\n\nTwo places that reached lazily-initialised modules through the bundler shim now require the bundled chunk directly: the MCP client used by the new sync code, and the handler behind the \"MCP server requests your input\" dialog. Same behaviour, different bundle mechanics.\n\n**Evidence**\n\n`.mcpElicitationHandlerModule()`\n\n- Area: Startup\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}