unstale

npm / bun-pty

bun-pty

What changed in bun-pty 0.5, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-28.

5 breaking2 behavior and defaults5 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli 0.2.9 on npm

bun-pty 0.512 changes

Breaking changes 5

  • When the child inherits process.env on Unix, the parent's COLUMNS and LINES are dropped.

    0.5.0release notes

  • When provided, env replaces the child's environment instead of being merged with the parent's; spread process.env to inherit variables.

    0.5.0release notes

  • If env has no PATH, bare program names are still found using the parent's PATH, which is not passed to the child.

    0.5.0release notes

  • On Unix, PWD is set from cwd when building the child's environment.

    0.5.0release notes

  • When the child inherits process.env on Unix, the parent's tmux and screen variables are dropped.

    0.5.0release notes

Behavior and default changes 2

  • Without env, the child receives the current process.env, so changes made at runtime reach it.

    0.5.0release notes

  • The name option is now optional, and env: process.env now type-checks.

    0.5.0release notes

Fixes and other changes 5

  • Importing bun-pty no longer throws when no native library file is found; the error is deferred to spawn(), while the load failure is still logged at import.

    0.5.2release notes

  • When the native library fails to load, spawn() now throws a clear error containing the library path and dlopen error instead of an undefined-property error.

    0.5.2release notes

  • Test files are no longer included in the npm package, so consumers receive a package without src/*.test.ts files.

    0.5.1release notes

  • On Windows, an empty env map keeps the parent's environment.

    0.5.0release notes

  • On Unix, TERM is set from the name option, then from TERM in the environment, then to xterm.

    0.5.0release notes