docs: Clarify that console.error appears in console but uses stderr

[ezra-ramatong]

Description

Clarified misleading description of console.error behavior in the stdout/stderr documentation. The previous text incorrectly stated that console.error "will not appear in the console" when it actually does appear in the console but uses the stderr stream.

Validation

The change is a simple text clarification in documentation. Reviewers should verify that the new wording accurately describes console.error behavior - that it appears in the console like normal output but uses stderr instead of stdout.

Related Issues

None - this is a standalone documentation improvement.

Check List

• I have read the Contributing Guidelines and made commit messages that follow the guideline.
• I have run pnpm format to ensure the code follows the style guide.
• I have run pnpm test to check if all tests are passing.
• I have run pnpm build to check if the website builds without errors.
• I've covered new added functionality with unit tests if necessary.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
nodejs-org	✅ Ready (Inspect)	Visit Preview	Jul 1, 2025 11:16am

[Copilot]

Pull Request Overview

This PR improves the documentation for console.error by clarifying that, although error messages are sent to stderr, they still appear in the console.

• Clarifies the behavior of console.error output
• Updates the existing misleading description in the documentation

Comments suppressed due to low confidence (1)

apps/site/pages/en/learn/command-line/output-to-the-command-line-using-nodejs.md:168

• The clarification is an improvement; however, consider explicitly mentioning that error messages are printed via stderr to remove any potential ambiguity.

It will appear in the console, but can be handled separately from regular output.

[mikeesto]

LGTM, thanks

[AugustinMauroy]

LGMT ! Thanks for your first contribution

[github-actions]

Lighthouse Results

URL	Performance	Accessibility	Best Practices	SEO	Report
/en	🟢 99	🟢 100	🟢 100	🟢 91	🔗
/en/about	🟢 100	🟢 96	🟢 100	🟠 82	🔗
/en/about/previous-releases	🟢 99	🟢 96	🟢 100	🟠 83	🔗
/en/download	🟢 99	🟢 100	🟢 100	🟢 91	🔗
/en/blog	🟢 100	🟢 100	🟢 96	🟢 92	🔗

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.42%. Comparing base (c15a2a3) to head (d8d130a).
Report is 4 commits behind head on main.

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7913      +/-   ##
==========================================
- Coverage   75.42%   75.42%   -0.01%     
==========================================
  Files          96       96              
  Lines        8355     8354       -1     
  Branches      219      219              
==========================================
- Hits         6302     6301       -1     
  Misses       2051     2051              
  Partials        2        2              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.