Introduction

In Node.js you usually do not change the terminal's actual font. What you can control is the text color and style emitted to the terminal, typically by writing ANSI escape sequences directly or by using a small library that wraps them.

Use ANSI Escape Codes Directly

The terminal understands ANSI escape sequences for color and formatting. That means a plain console.log call can print colored text without any dependency.

console.log("\x1b[31mThis text is red\x1b[0m");
console.log("\x1b[32mThis text is green\x1b[0m");
console.log("\x1b[33mThis text is yellow\x1b[0m");

The \x1b[0m sequence resets the style back to the terminal default. Without it, later output may keep the same color.

A few common foreground codes are:

• '31 red'
• '32 green'
• '33 yellow'
• '34 blue'
• '35 magenta'
• '36 cyan'

This is the lightest-weight solution and works well for quick scripts.

Use a Library for Cleaner Code

For production code, raw escape codes become noisy. A formatting library makes logs easier to read and maintain.

A lightweight option is picocolors:

npm install picocolors

Example usage:

1import pc from "picocolors";
2
3console.log(pc.red("Error message"));
4console.log(pc.green("Success message"));
5console.log(pc.yellow("Warning message"));

If your project uses CommonJS:

const pc = require("picocolors");
console.log(pc.cyan("Informational output"));

Libraries like this also handle nested styles more cleanly than manual escape sequences.

Combine Color With Other Emphasis

Terminal styling is not limited to color. You can also add bold, dim, underline, or background colors if the terminal supports them.

Using raw ANSI:

console.log("\x1b[1m\x1b[31mBold red text\x1b[0m");

Using a library:

import pc from "picocolors";

console.log(pc.bold(pc.red("Bold red text")));

This is useful for differentiating errors, warnings, and headings in CLI tools.

Remember That Support Depends on the Terminal

Node prints sequences to stdout or stderr, but the terminal decides how to render them. Most modern terminals support ANSI colors, but behavior can differ when output is:

• redirected to a file
• viewed in a minimal CI console
• consumed by another process
• displayed in an older shell environment

If your script may run in many environments, detect whether color should be enabled or provide a --no-color option.

Use console.error and console.warn Intentionally

Color can improve log clarity, but it should reinforce meaning rather than replace it. Use the right output stream too.

1import pc from "picocolors";
2
3console.log(pc.green("Build completed"));
4console.warn(pc.yellow("Using fallback config"));
5console.error(pc.red("Build failed"));

This keeps terminal color aligned with semantics and plays better with shell pipelines.

Common Pitfalls

• Expecting Node.js to change the terminal's actual font is a category mistake. It can style output, not reconfigure the terminal application itself.
• Forgetting the reset sequence when using raw ANSI codes causes later log lines to inherit the same style.
• Hardcoding colorful output without considering redirected logs can make files harder to read.
• Using raw escape codes everywhere makes maintenance harder once the CLI grows beyond a few lines.
• Relying only on color to convey severity is an accessibility problem; combine color with good wording or symbols.

Summary

• In Node.js, changing console color means styling terminal output, usually with ANSI escape codes.
• Raw ANSI sequences are enough for quick scripts and simple logging.
• A library such as picocolors makes colored output cleaner and easier to maintain.
• Terminal support varies, so color should be treated as a presentation layer, not a guarantee.
• Use color to reinforce meaning, not to replace clear log structure.