feat(logger-middleware): add support for color and pretty formatters

[agionoja]

This adds optional colorized output and human-readable formatters for durations and file sizes.

New features:

• colors option for colorized output (off by default)
• formatDuration() - formats ms as "1.20s", "45ms", etc.
• formatFileSize() - formats bytes as "1.2 kB", "120 B", etc.
• Updated default format to use %durationPretty and %contentLengthPretty

Colors (when enabled):

• Status codes: green (2xx), cyan (3xx), yellow (4xx), red (5xx)
• Durations: green (<100ms), yellow (100-500ms), magenta (500ms-1s), red (>1s)
• Methods: GET (green), POST (cyan), PUT/PATCH (yellow), DELETE (red), HEAD/OPTIONS (magenta)
• Content length: cyan (1kB-100kB), yellow (100kB-1MB), red (>1MB)

No breaking changes - colors default to off.

[mjackson]

Let's default to using color when we detect we are in a TTY. This is going to be tricky since we don't want to lose the ability to run logger middleware in browser/service worker environment.

Something like this could work:

const useColor = typeof process !== 'undefined' &&
  process.stdout.isTTY &&
  process.env.NO_COLOR == null

function colorize(text: string, color: string) {
  return useColor ? `${color}${text}${reset}` : text
}

[MichaelDeBoey]

@agionoja Something seems to have gone wrong with rebasing on main

[agionoja]

@agionoja Something seems to have gone wrong with rebasing on main

Sorry about that. I've fixed it.

[agionoja]

Let's default to using color when we detect we are in a TTY. This is going to be tricky since we don't want to lose the ability to run logger middleware in browser/service worker environment.

Something like this could work:

const useColor = typeof process !== 'undefined' &&
  process.stdout.isTTY &&
  process.env.NO_COLOR == null

function colorize(text: string, color: string) {
  return useColor ? `${color}${text}${reset}` : text
}

I've done as you suggested. Now we only use colors in supported envs and if the user explicitly uses the colors option.