Question 1

How do I read stdin in Node.js with get-stdin?

Accepted Answer

Import get-stdin and use `await getStdin()` for string input or `getStdin.buffer()` for binary. For interactive input, set `allowTTY: true` and close stdin with Ctrl+D (Unix) or Ctrl+Z (Windows), as shown in the examples.

Question 2

get-stdin vs Node.js native stream consumers: which should I use?

Accepted Answer

get-stdin offers a simpler, promise-based API with built-in TTY handling, while native `streamConsumers.text()` is available in Node.js 17.5+. Use get-stdin for consistency across older Node versions or if you prefer its API; otherwise, native methods reduce dependencies.

Question 3

How to test code that uses get-stdin?

Accepted Answer

Use the `stdin` option to pass a custom readable stream, such as a mock stream in tests. This allows simulating stdin input without actual terminal interaction, as mentioned in the API documentation.

Question 4

get-stdin or get-stream for reading streams in Node.js?

Accepted Answer

get-stdin is specifically designed for stdin, while get-stream handles any readable stream. Choose get-stdin for CLI input scenarios; for broader stream reading, get-stream is more versatile.

Question 5

Why does my get-stdin script hang in interactive mode?

Accepted Answer

By default, get-stdin avoids hanging in TTY by resolving immediately. To read interactively, set `allowTTY: true` and ensure stdin is closed with EOF (Ctrl+D or Ctrl+Z), as explained in the README.

Question 6

How to handle binary data from stdin with get-stdin?

Accepted Answer

Use `getStdin.buffer()` to get stdin as a Uint8Array. This is useful for processing binary files or data piped from commands, and it mirrors the string API for consistency.

get-stdin

What is get-stdin?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions