fix: rebuild node-pty from source for Node.js 22+ compatibility - #2
Closed
eYdr1en wants to merge 1 commit into
Closed
fix: rebuild node-pty from source for Node.js 22+ compatibility#2eYdr1en wants to merge 1 commit into
eYdr1en wants to merge 1 commit into
Conversation
The prebuilt node-pty binaries don't support Node.js 22's ABI version (127), causing `posix_spawnp failed` errors when spawning PTY sessions. This fix adds a `npm rebuild node-pty --build-from-source` step after npm install to ensure the native module is compiled for the user's specific Node.js version. Fixes PTY spawn failures on systems running Node.js 22+.
Ark0N
commented
Feb 18, 2026
Owner
Fixed in 50b1718 — postinstall now runs npm rebuild node-pty --build-from-source for Node.js 22+. |
michael-ltm pushed a commit
to michael-ltm/Codeman
that referenced
this pull request
Jul 4, 2026
- Ark0N#2: drop the "本机"/"(本机)" special-case labels in the fleet device panel, device <select>, and welcome device row — show the real device name (local = os.hostname()). A remote viewer sees the true machine name. - Ark0N#4: persist closed fleet tabs to localStorage (codeman:fleet-hidden-tabs) so a close survives reloads; prune keys whose session is gone (bounded set); add a reopen path — clicking a device-panel session row calls openFleetSessionTab() to unhide + selectSession. - Ark0N#5: submitFleetCreateSession now opens + selects the new session as a tab (mirrors _quickStartRemote) and toasts "已在 <设备名> 创建并打开". Local (non-fleet) session close/behavior is byte-identical: the persistent hidden set is fleet-key-only (isFleetKey/_looksLikeFleetKey guards), and requestCloseSession still routes local keys to the confirm modal untouched. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
npm rebuild node-pty --build-from-sourcestep afternpm installin the installerposix_spawnp failederrors when using Node.js 22+Problem
The prebuilt
node-ptybinaries (v1.1.0) don't support Node.js 22's ABI version (127). This causes the following error when starting Claudeman:Solution
Rebuild
node-ptyfrom source during installation to ensure it's compiled for the user's specific Node.js version and architecture.Testing
Verified on macOS (Apple Silicon, arm64) with Node.js v22.19.0:
posix_spawnp failed🤖 Generated with Claude Code