2022-06-08
1385
#node
Oluwasegun Kayode
113932
Jun 8, 2022 â‹… 4 min read

Using stdout, stdin, and stderr in Node.js

Oluwasegun Kayode I love every technology and the solution it provides.

Recent posts:

Fix over-caching with dynamic IO caching in Next.js 15

Next.js 15 caching overhaul: Fix overcaching with Dynamic IO and the use cache directive.

David Omotayo
Aug 6, 2025 â‹… 10 min read
LLMs are facing a QA crisis here’s how we could solve it

LLMs are facing a QA crisis: Here’s how we could solve it

LLM QA isn’t just a tooling gap — it’s a fundamental shift in how we think about software reliability.

Rosario De Chiara
Aug 4, 2025 â‹… 7 min read

Windsurf vs. Cursor: When to choose the challenger

Windsurf AI brings agentic coding and terminal control right into your IDE. We compare it to Cursor, explore its features, and build a real frontend project.

Chizaram Ken
Jul 31, 2025 â‹… 9 min read

The CSS if() function: Conditional styling will never be the same

The CSS Working Group has approved the if() function for development, a feature that promises to bring true conditional styling directly to our stylesheets.

Ikeh Akinyemi
Jul 30, 2025 â‹… 12 min read
View all posts

4 Replies to "Using <code>stdout</code>, <code>stdin</code>, and <code>stderr</code> in Node.js"

  1. Great article. Thanks. I’m by no means an expert, but re: your comment “It is pretty straightforward to understand why stdin and stdout exist. However, stderr seems pretty odd.” and very much in keeping with your explanation, stdout and stderr are separate channels and may, for example, be separately redirected to two different files. So stderr is sometimes very useful for that purpose, etc.

  2. I came across this while searching about an error that occured while running my react projects. The error occurs while running build command on our project using git bash. Following is the error: > @mo/[email protected] prepare
    > npm run build:dist

    npm ERR! Cannot read properties of undefined (reading ‘stdin’)

    npm ERR! A complete log of this run can be found in: C:\Users\Firmusoft\AppData\
    Local\npm-cache\_logs\2023-10-12T04_41_27_328Z-debug-0.log

    Does anyone have an idea about this?. I have uninstalled and reinstalled Node and npm and have also removed package-lock.json and cleared npm cache, but still the error persists.
    My Node version is 20.2.0 and npm version is 9.6.6 .

    Thanks!!

Leave a Reply