ehmicky

Only the environment variables set in the Netlify App UI can currently be used in Netlify Functions. However, there is a workaround: [the `netlify-plugin-inline-functions-env` plugin](https://github.com/bencao/netlify-plugin-inline-functions-env) is injecting/templating any environment variable...

Sounds good. :+1:

I found out two TypeScript bugs which were blocking this PR, but worked around it. The new exported types are: `ExecaMethod`, `ExecaNodeMethod`, `ExecaScriptMethod`, `ExecaSyncMethod`, `ExecaScriptSyncMethod`. They take an optional `Options`/`SyncOptions`...

This was released in [`9.2.0`](https://github.com/sindresorhus/execa/releases/tag/v9.2.0).

Thanks @huang-julien! Let's first figure out the underlying problem in the issue at #1102. I am suspecting it to be slightly different that it seems.

Closing per https://github.com/sindresorhus/execa/issues/1102#issuecomment-2146787524

Hi @huang-julien, Thanks for reporting this! I cannot easily setup WSL on my machine at the very moment, so we might need a few back-and-forth going through your reproduction example....

Thanks! What's happening is the following: Windows does not support Unix-style signals. Node.js emulates a handful of signals, but it has some limitations. You can find more details [here](https://nodejs.org/api/process.html#signal-events) and...

Thanks for posting this issue, as it gave me the idea to: - Add a way to gracefully terminate in a cross-platform way, which will be available in the upcoming...

The new features mentioned in my previous comment have just been released in [`9.2.0`](https://github.com/sindresorhus/execa/releases/tag/v9.2.0).