Troubleshooting

This guide helps you diagnose and resolve common issues when using nstypocolors in applications and CLIs.

Colors Not Appearing

Possible causes

• The terminal does not support ANSI colors
• Output is being redirected to a file or pipe
• Color output is disabled by the environment

Solutions

• Use a modern terminal (Windows Terminal, iTerm2, Kitty, Alacritty)
• Avoid piping output when expecting colors
• Test with a minimal script

import { logSuccess } from 'nstypocolors'

logSuccess('Color test')

const { logSuccess } = require('nstypocolors')

logSuccess('Color test')

Gradients Look Incorrect or Noisy

Possible causes

• Overusing gradients for long output
• Applying gradients to paragraphs or detailed logs

Recommended fix

Use gradients only as visual anchors, such as headers or state changes.

logBuild('Starting process')
console.log('Step 1 completed')

logBuild('Starting process')
console.log('Step 1 completed')

Colors Break When Redirecting Output

Example:

my-cli > output.txt

When redirected, ANSI escape codes are written into the file.

Solutions

• Detect non-TTY output and disable colors
• Provide a --no-color flag in your CLI

if (process.stdout.isTTY) {
  logInfo('TTY detected')
} else {
  console.log('Non-TTY output')
}

if (process.stdout.isTTY) {
  logInfo('TTY detected')
} else {
  console.log('Non-TTY output')
}

Windows-Specific Issues

Older Windows shells may not render ANSI colors correctly.

Recommended fixes

• Use Windows Terminal
• Update Node.js to a recent LTS version
• Avoid legacy Command Prompt when possible

Very Short Messages Look Plain

Gradients may appear subtle for very short strings. This is expected behavior.

logSuccess('OK')
logWarn('!')

logSuccess('OK')
logWarn('!')

Short messages should rely on wording rather than visual complexity.

Unexpected Line Breaks

Common causes

• Manual \n usage
• Logging wrappers adding extra newlines

Fix

Avoid chaining logs with manual spacing.

logInfo('Step started')
logSuccess('Step completed')

logInfo('Step started')
logSuccess('Step completed')

Mixing Colored and Plain Logs

If output feels inconsistent, apply a layered strategy:

• Gradient → major state changes
• Plain text → details and progress
• Error colors → failures only

This approach keeps logs readable and intentional.

Performance Concerns

nstypocolors is lightweight, but excessive logging can still impact performance.

Best practices

• Avoid logging inside tight loops
• Disable verbose output in production
• Enable detailed logs via flags like --verbose

When Things Still Don’t Work

If issues persist:

• Verify your Node.js version
• Test in a clean environment
• Reduce the problem to a minimal reproduction

When opening an issue, include:

• Node.js version
• Terminal name
• Sample output

Final Note

Most issues with colored output are environment-related, not code-related.

Always prioritize clear, meaningful text—and let color enhance, not replace, communication.