execa - npm Package Compare versions

Comparing version 7.1.1 to 7.2.0

index.d.ts

		@@ -367,2 +367,7 @@ import {type Buffer} from 'node:buffer';
		signalDescription?: string;

		/**
		The `cwd` of the command if provided in the command options. Otherwise it is `process.cwd()`.
		*/
		cwd: string;
		};
		@@ -464,3 +469,3 @@
		/**
		Same as the original [`child_process#kill()`](https://nodejs.org/api/child_process.html#child_process_subprocess_kill_signal), except if `signal` is `SIGTERM` (the default value) and the child process is not terminated after 5 seconds, force it by sending `SIGKILL`.
		Same as the original [`child_process#kill()`](https://nodejs.org/api/child_process.html#child_process_subprocess_kill_signal), except if `signal` is `SIGTERM` (the default value) and the child process is not terminated after 5 seconds, force it by sending `SIGKILL`. Note that this graceful termination does not work on Windows, because Windows [doesn't support signals](https://nodejs.org/api/process.html#process_signal_events) (`SIGKILL` and `SIGTERM` has the same effect of force-killing the process immediately.) If you want to achieve graceful termination on Windows, you have to use other means, such as [`taskkill`](https://github.com/sindresorhus/taskkill).
		*/
		@@ -601,3 +606,4 @@ kill(signal?: string, options?: KillOptions): void;
		isCanceled: false,
		killed: false
		killed: false,
		cwd: '/path/to/cwd'
		}
		@@ -685,3 +691,4 @@ \*\/
		isCanceled: false,
		killed: false
		killed: false,
		cwd: '/path/to/cwd'
		}
		@@ -688,0 +695,0 @@ \*\/

lib/error.js

		@@ -0,1 +1,2 @@
		import process from 'node:process';
		import {signalsByName} from 'human-signals';
		@@ -39,3 +40,3 @@
		killed,
		parsed: {options: {timeout}},
		parsed: {options: {timeout, cwd = process.cwd()}},
		}) => {
		@@ -71,2 +72,3 @@ // `signal` and `exitCode` emitted on `spawned.on('exit')` event can be `null`.
		error.stderr = stderr;
		error.cwd = cwd;

		@@ -73,0 +75,0 @@ if (all !== undefined) {

package.json

		{
		"name": "execa",
		"version": "7.1.1",
		"version": "7.2.0",
		"description": "Process execution for humans",
		@@ -41,3 +41,4 @@ "license": "MIT",
		"path",
		"local"
		"local",
		"zx"
		],
		@@ -65,3 +66,3 @@ "dependencies": {
		"tsd": "^0.25.0",
		"xo": "^0.53.1"
		"xo": "^0.54.2"
		},
		@@ -68,0 +69,0 @@ "c8": {

readme.md

		@@ -11,2 +11,32 @@ <picture>

		<br>

		---

		<div align="center">
		<p>
		<p>
		<sup>
		<a href="https://github.com/sponsors/sindresorhus">Sindre's open source work is supported by the community</a>
		</sup>
		</p>
		<sup>Special thanks to:</sup>
		<br>
		<br>
		<a href="https://transloadit.com">
		<picture>
		<source width="360" media="(prefers-color-scheme: dark)" srcset="https://sindresorhus.com/assets/thanks/transloadit-logo-dark.svg">
		<source width="360" media="(prefers-color-scheme: light)" srcset="https://sindresorhus.com/assets/thanks/transloadit-logo.svg">
		<img width="360" src="https://sindresorhus.com/assets/thanks/transloadit-logo.svg" alt="Transloadit logo">
		</picture>
		</a>
		<br>
		<br>
		</p>
		</div>

		---

		<br>

		## Why
		@@ -291,2 +321,4 @@

		Note that this graceful termination does not work on Windows, because Windows [doesn't support signals](https://nodejs.org/api/process.html#process_signal_events) (`SIGKILL` and `SIGTERM` has the same effect of force-killing the process immediately.) If you want to achieve graceful termination on Windows, you have to use other means, such as [`taskkill`](https://github.com/sindresorhus/taskkill).

		##### options.forceKillAfterTimeout
		@@ -434,2 +466,8 @@

		#### cwd

		Type: `string`

		The `cwd` of the command if provided in the [command options](#cwd-1). Otherwise it is `process.cwd()`.

		#### message
		@@ -436,0 +474,0 @@

New alerts