Back to Explore

nexdrew/ansi-align

GitHub
1 watchersOpen source

Last release:

Library for aligning blocks of text for command line interfaces, with support for ANSI escape codes. It can center or right-align lines while ignoring ANSI codes, and provides an `ansiAlign(text, [opts])` API with options for alignment, splitting, and padding.

Project status

  • The GitHub source (nexdrew/ansi-align) appears effectively dormant, with the last upstream push on 2021-09-27, far before today (2026-08-12), so it does not look actively maintained.
  • Update cadence is very infrequent, with published updates spanning multiple years (v3.0.1 in 2021, v3.0.0 in 2018, v2.0.0 in 2017).

AI summary generated

AI-generated from public sources. May be inaccurate. Report

Recent updates

  • v3.0.1

    v3.0.1 does not appear to change the library’s runtime alignment logic directly, instead it updates package metadata, CI configuration, and dependency versions. The only functional risk area is a dependency bump (string-width) that can change how character widths are computed, which can affect alignment output.

  • v3.0.0

    No release notes were provided for v3.0.0. The code diff shows a major version bump (2.0.0 to 3.0.0) with dependency updates and a change to supported Node versions in CI.

  • v2.0.0

    Release v2.0.0 was published on 2017-05-01, but no release notes content was provided by the publisher. As a result, there is no documented information here about new features, bug fixes, security updates, or breaking changes.

  • v1.1.0

    This release (v1.1.0) adds support for left alignment by treating `align: 'left'` as a no-op and introduces a convenience alias `ansiAlign.left`. The actual code behavior also changes how the alignment width delta function is chosen for alignment modes other than the explicitly handled ones. No release notes were provided in the supplied release_notes input.

    BreakingFeatures
  • v1.0.0

    Release v1.0.0 was published on 2016-04-30, but no release notes were provided by the publisher. As a result, there is not enough documented information to identify new features, bug fixes, security updates, breaking changes, or migration requirements.