next.js
0d881404 - refactor(turbopack-cli-utils): replace crossterm with owo-colors (#97855)

Commit
79 days ago
refactor(turbopack-cli-utils): replace crossterm with owo-colors (#97855) > Replaces #97581, which was **not merged**. Reordering this stack briefly left that PR > pointing at a base branch that had come to contain its own head commit, so GitHub closed it > as merged and deleted its branch. Nothing from it reached `canary`. It had been approved; > this PR is the same commit (`e1d79b6f4c`), restored, and needs review again. Sorry for the churn. ### What? `turbopack-cli-utils` uses `owo-colors` instead of `crossterm` for issue formatting. ### Why? Two reasons: - `crossterm` 0.26 has no wasm backend, and fails to compile for wasm with 8 errors inside the crate itself. - It was pulling its weight for very little: the only uses were `StyledContent` and `Stylize` in `issue.rs`, and `owo-colors` — already a dependency of that same file — covers all of them. ### How? Swap the trait usage over and return `String` from `show_all_message` rather than `StyledContent<String>`. Rendered output is unchanged. This also removes `crossterm`, `crossterm_winapi`, `mio 0.8`, `signal-hook` and `signal-hook-mio` from `Cargo.lock` (and lets cargo drop the `mio 1.2` disambiguation, since only one `mio` remains). <!-- NEXT_JS_LLM --> <!-- fleet b6d0486f-97c7-42a7-bdaf-3490774cdec3 --> Co-authored-by: vercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com> Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
Author
Parents
Loading