## TL;DR

The maintainer traced it to process.stdout.columns being undefined on CI and pushed a fix that landed in Portman 1.8.0. Upgrade, or as a workaround ensure the CI step allocates a TTY/column width.

## The error

```text
Invalid count value on CI
```

## Fix

1. The maintainer traced it to process.stdout.columns being undefined on CI and pushed a fix that landed in Portman 1.8.0.
   Expected: You get the expected result; the problem is gone.
2. Upgrade, or as a workaround ensure the CI step allocates a TTY/column width.
   Expected: You get the expected result; the problem is gone.
3. Re-run the original operation and confirm the error is gone.
   Expected: no error, normal output.

## When to use

- You hit this exact error with Portman crashes with RangeError.
- The symptom matches: Invalid count value on CI.

## When NOT to use

- A different error message from Portman crashes with RangeError; the cause here is specific to this error.
- Unrelated Portman crashes with RangeError issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Portman crashes with RangeError (mentions 1.8.0).

## Variant phrasings

### Invalid count value on CI

## Why it happens

GitHub issue on apideck-libraries/portman: running Portman on CircleCI throws RangeError: Invalid count value. Root cause: some CI environments report no (or a tiny) stdout column width, and the column-formatting code choked on it.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- Behavior can change between releases; the linked source reflects the versions above.
- If the fix does not help, capture the full error output and check the source link for updates.