{"version":"2.1.227","anchor":"layout-results-cached-on-nodes-instead-of-a-side-table","canonical_anchor":"layout-results-cached-on-nodes-instead-of-a-side-table","heading":"Layout results cached on nodes instead of a side table","tier":"internal","area":"Terminal Rendering","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/layout-results-cached-on-nodes-instead-of-a-side-table","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Layout results cached on nodes instead of a side table\n\nLayout results are cached on each node rather than in a shared table.\n\n**What**\n\nThe terminal renderer now stores each node's computed layout on the node itself rather than in a separate lookup table, and the layout engine carries its own counters for nodes visited, measure calls, cache hits and live nodes in place of module-level functions.\n\n**Evidence**\n\n`cachedLayout`\n\n- Area: Terminal Rendering\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}