<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Spawn on recca0120 Tech Notes</title><link>https://recca0120.github.io/en/tags/spawn/</link><description>Recent content in Spawn on recca0120 Tech Notes</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 26 Apr 2026 04:55:00 +0800</lastBuildDate><atom:link href="https://recca0120.github.io/en/tags/spawn/index.xml" rel="self" type="application/rss+xml"/><item><title>Node.js spawn stdout Gets Truncated: Compared 6 Fixes, Only the File Trick Works</title><link>https://recca0120.github.io/en/2026/04/26/nodejs-spawn-stdout-truncated/</link><pubDate>Sun, 26 Apr 2026 04:55:00 +0800</pubDate><guid>https://recca0120.github.io/en/2026/04/26/nodejs-spawn-stdout-truncated/</guid><description>When spawning a high-output CLI in Node.js, the last few KB vanish on process.exit(). After comparing 6 solutions, the only reliable cross-platform stdlib fix is piping the child stdout fd to a file.</description><content:encoded>&lt;![CDATA[When spawning a high-output CLI in Node.js, the last few KB vanish on process.exit(). After comparing 6 solutions, the only reliable cross-platform stdlib fix is piping the child stdout fd to a file.<br/><img src="https://recca0120.github.io/2026/04/26/nodejs-spawn-stdout-truncated/featured.png" alt="Featured image"/>]]></content:encoded><enclosure url="https://recca0120.github.io/2026/04/26/nodejs-spawn-stdout-truncated/featured.png" type="image/png" length="0"/><media:content url="https://recca0120.github.io/2026/04/26/nodejs-spawn-stdout-truncated/featured.png" medium="image"/><category>Node.js</category><category>stdio</category><category>spawn</category><category>DevOps</category></item></channel></rss>