{"version":"2.1.222","anchor":"task-output-files-use-a-memoized-path-and-lazy-directory-cre","canonical_anchor":"task-output-files-use-a-memoized-path-and-lazy-directory-cre","heading":"Task output files use a memoized path and lazy directory creation","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/task-output-files-use-a-memoized-path-and-lazy-directory-cre","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Task output files use a memoized path and lazy directory creation\n\nTask output files skip repeated path work and only create folders when actually writing.\n\n**What**\n\nTask output writing resolves its file path once per task and creates the containing directory only when the file is opened, replacing an upfront directory-creation step.\n\n**Details**\n\n- `<taskId>.output` is resolved through a per-task path cache\n- The parent directory is created at open time with `mkdir(dirname, { recursive: true })`\n- The previous upfront directory creation helper was removed\n- The cache entry is dropped when the task output is flushed, cleared or cleaned up\n\n**Evidence**\n\n`.output`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}