fix: warnings that name project files print control characters as visible escapes (#7863)

* fix: warnings that name project files print control characters as visible escapes

The CLI already escaped control characters in the text its own commands
print, but warnings from core, producer and engine went to the terminal
raw. A composition whose sub-composition path held ESC or BEL still
drove the terminal through the bundler's "Skipping sub-composition"
warning in `info --media` and `snapshot`.

terminalText moves to core so there is one sanitiser, the CLI imports it
from there, and the library warnings that carry project text (the
bundler, the producer logger, the file server, render path skips, asset
load failures, FrameCapture, the import map, fonts, figma and atomic
file warnings) pass that text through it.

* fix: every library warning that carries project text escapes control characters
This commit is contained in:
Miguel Ángel
2026-11-16 04:56:36 +00:00
committed by GitHub
parent 8e8eeb2059
commit d42bbd67f4
33 changed files with 261 additions and 70 deletions
@@ -3,7 +3,7 @@ import { mkdirSync, mkdtempSync, rmSync, writeFileSync } from "node:fs";
import { tmpdir } from "node:os";
import { join } from "node:path";
import { createStudioServer, type StudioServer } from "./studioServer.js";
import { terminalText } from "../utils/terminalText.js";
import { terminalText } from "@hyperframes/core";
const mocks = vi.hoisted(() => ({
resolveRenderBrowser: vi.fn(),