I built Inklin because I wanted a better terminal styling experience for Node.js

When working on CLI tools, I kept running into the same limitations with existing styling libraries.

They were good—but once you start building more complex terminal output, a few problems start to show up:

So I built Inklin.

It’s a small terminal styling utility for Node.js that focuses on predictable behavior, modern module support, and minimal overhead.

What Inklin does

Inklin is not trying to replace everything—it’s focused on a few specific improvements.

Most terminal styling libraries reset styles when a nested style ends.

That creates unexpected output when combining styles.

Inklin instead tracks a style stack, so parent styles are restored automatically.

Example idea:

red("Error: " + blue("file not found"))

After blue() ends, the output correctly returns to red() instead of resetting to default.

This makes deeply nested styling more predictable in real CLI output.

One of the most annoying parts of modern Node.js libraries is module compatibility.

Inklin works in both environments without extra setup:

No dual package confusion, no build hacks required for basic usage.

Inklin includes support for:

These are useful for modern CLI tools where terminals are no longer just plain text environments.

The goal was to keep the core small and predictable.

No large dependency tree, no unnecessary abstractions.

How it works internally

Under the hood, Inklin uses a lazy Proxy-based chaining system.

Instead of eagerly computing styles, it builds them dynamically when accessed.

This allows:

It also uses a recursive structure to manage style composition, which helps keep nesting behavior consistent.

Example usage

import inklin from "inklin";

console.log(
inklin.red.bold("Error:") + " something went wrong"
);

Or chain-style:

inklin.bold.blue("Hello world").log();

Why I built it

The goal wasn’t to reinvent terminal styling.

It was to explore a simpler, more predictable API for CLI output while avoiding some of the edge-case issues I kept running into in real projects.

Especially around:

Repo

Feedback welcome

I’d especially appreciate feedback on: