"Bash + Node.js + stdin\/stdout 重定向：错误“不是 tty”"

Question

This problem may be Windows-specific. I have not tested it on Linux or Mac.

Answer 1

Create a file my-cli :

#!/bin/sh

node "path/to/my-cli.js" "$@"
exit $?

Call ./my-cli > foo.txt or ./my-cli < foo.txt .

This also works with arguments: ./my-cli --answer 42 > foo.txt

Answer 2

This happens because Git for Windows on default setup will source this file /etc/profile.d/aliases.sh which will do alias node="winpty node.exe" , which is required for interactive usage with node (as well as other programs like python ,...). So when you invoke node xxx <yyy >zzz , your shell is actually calling winpty node xxx under the hood

winpty works by starting the winpty-agent.exe process with a new, hidden console window, which bridges between the console API and terminal input/output escape codes. It polls the hidden console's screen buffer for changes and generates a corresponding stream of output.

, but the side effect is that the stdin and stdout is not recognised as tty's.

So when piping or redirecting, you would want to invoke the node binary itself and not the alias. There are some ways to achieve this:

1. Wrap in a shell script which would directly call node since non-interactive shell does not source the aliases.sh file. See the other answers (both sh and bash work)

2. Call with
   env node my-cli.js > foo.txt or
   command node my-cli.js > foo.txt

env runs the command in a default environment, the effect is like that of the above method; while command is a bash shell built-in that is used to bypass aliases.

3. Call like
   \\node my-cli.js > foo.txt or
   'node' my-cli.js > foo.txt or
   "node" my-cli.js > foo.txt

The backslash and quotation are constructs to explicitly bypass aliasing.

4. Call using
   node.exe my-cli.js > foo.txt or
   /full/path/to/node my-cli.js > foo.txt or
   relative/path/to/node my-cli.js > foo.txt

The alias is for node , not node.exe nor path/to/node , which still points to the actual binary.

A way to expand on these solutions is to write a wrapper script that detects piping / redirection (which is in itself a whole other challenge tbh) which will decide to use winpty or not.

Answer 3

sh -c 'node my-cli.js' > foo.txt对我sh -c 'node my-cli.js' > foo.txt

Answer 4

Since I'm here in 2022 having this same issue in GitBash, one of the other answers pointed me to the simplest solution.