fix(client): fix dev mode hanging on Windows #1051
Merged
+14
−4
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 run dev:windowshanging on Windows after PR Re-enable inspector auto-open & reloads post security fixes #513 introduced a regressionstdiooption instead of spawn-rx'sstdinoption to ignore stdinProblem
PR #513 unified the dev scripts and attempted to handle Windows stdin with:
However, spawn-rx's
stdinoption expects anObservable<string>, not a string value. The library strips out thestdinoption before passing it to Node'schild_process.spawn, which means the setting was silently ignored. This caused tsx watch to hang waiting for stdin input on Windows.Solution
Use Node's native
stdiooption instead:This option is passed through correctly by spawn-rx to the underlying spawn call, properly simulating the previous
< NULshell redirection behavior.Test plan
npm run dev:windowson Windows - server and client both start successfullynpm run devon Windows - also works (same code path)Fixes #550
🤖 Generated with Claude Code