{"version":"2.1.248","anchor":"build-reshaped-lazy-module-wrappers-flattened-cross-module-c","canonical_anchor":"build-reshaped-lazy-module-wrappers-flattened-cross-module-c","heading":"Build reshaped: lazy module wrappers flattened, cross-module calls go through chunk requires","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/build-reshaped-lazy-module-wrappers-flattened-cross-module-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Build reshaped: lazy module wrappers flattened, cross-module calls go through chunk requires\n\nThe bundle was flattened and more code now sits behind opaque chunk boundaries.\n\n**What**\n\nHundreds of lazily initialised module bodies are now plain top-level values, and several call sites reach other modules by requiring a numbered chunk file at runtime instead of an in-bundle handshake. Nothing changes for users, but more of the CLI's own code now sits behind chunk boundaries that are opaque to inspection.\n\n**Details**\n\n- Flattened contents include schemas, sets, regexes, AWS and Bedrock service metadata, and slash-command descriptors.\n- Call sites now using a chunk require include the MCP resource prefetcher, safe git executable resolution, the brief-mode check and session id compatibility conversion.\n\n**Evidence**\n\n`import.meta.require(\"\/$bunfs\/root\/chunk-XXXXXXXX.js\")`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}