Back to Explore

sindresorhus/restore-cursor

GitHub
1 watchersOpen source

Last release:

Restores the CLI cursor on exit, intended to prevent a hidden cursor from remaining hidden if your process crashes. It is meant for interactive TTY sessions only, and does nothing when run in a non-TTY context.

Project status

  • Maintenance status: The repo appears quiet, with the last upstream push on 2024-07-26 and no updates after that as of 2026-06-09. It does not look actively maintained right now.
  • Update cadence: Historically there were major updates in 2019 and 2021, then a gap until 2023-09-28, followed by another update in 2024-07-26 (which was a dependency-only style change). The overall cadence is sporadic, with a long current quiet period.

AI summary generated

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

Recent updates

  • v5.1.0

    v5.1.0 is described only as a dependency update. The code diff shows packaging metadata changes (adding a types entry and declaring sideEffects: false), plus runtime and dev dependency bumps.

  • v5.0.0

    v5.0.0 updates restore-cursor to target Node.js 18+ and changes how the cursor restoration escape sequence is emitted based on TTY presence. The main behavioral change is that cursor restoration no longer attempts to write control codes when the relevant output stream is not a TTY.

    Breaking
  • v4.0.0

    v4.0.0 converts restore-cursor to a pure ESM package and raises the minimum supported Node.js versions. The codebase was updated across JavaScript, TypeScript declarations, tests, and documentation to use ESM default export syntax.

    Breaking
  • v3.1.0

    Release v3.1.0 primarily adds TypeScript support via a new declaration file. The code diff also updates build and CI configuration to run TypeScript definition tests and linting. No runtime behavior changes to the main JavaScript module are visible in this diff.

    Features
  • v3.0.0

    v3.0.0 is a breaking release that raises the minimum supported Node.js version. If you are running this package on an older Node runtime, you will need to upgrade before upgrading to v3.0.0.

    Breaking