Commit activity
Last 12 weeks · 0 commits
Community health
4 of 6 standards met
85
✓README✓License✓Contributing✓Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Quiet · 3 discussions · Last activity 4mo ago
See all on GitHub →
Month ago, When I switch to I got I thought it's bug, so I switched to . but I just found that I should use as stdin. Is it possible to improve the error? Or maybe use instead?
Recent fixes
Fixes #112. Arbitrary strings passed to are now used directly as subprocess input. The four Node.js stdio modes (, , , and ) keep their existing behavior, and the existing form remains supported. The implementation only applies this shorthand to the top-level option, so , , and continue to follow Node.js semantics. Includes runtime tests for arbitrary and empty strings, the commonly mistyped value, the correct mode, TypeScript coverage, and documentation updates.
This adds , which is always set as a boolean, and is when a has been canceled by the option. This PR makes sure is if the subprocess is terminated by an unrelated to the option, e.g. if one of the streams emits an event due to an .
This change preserves so that callers can check if to know if a subprocess got cancelled or if it encountered some other error. Maintaining the error identity helps callers distinguish between the two.
Structured data for AI agents
Repository: sindresorhus/nano-spawn. Description: Tiny process execution for humans — a better child_process Stars: 590, Forks: 15. Primary language: JavaScript. Languages: JavaScript (92.7%), TypeScript (7.3%). License: MIT. Latest release: v2.1.0 (4mo ago). Open PRs: 0, open issues: 3. Last activity: 4mo ago. Community health: 85%. Top contributors: ehmicky, sindresorhus, fisker, Septh.