Closed lambdalisue closed 3 years ago
In case someone faced similar issue, our workaround for this issue for now is Does not work.
// deno-lint-ignore no-explicit-any
proc.kill((Deno as any).Signal.SIGTERM);
I'm sorry, I thought Deno.Signal.SIGTERM
is still available on Deno 1.14. My bad.
Using
Deno.Signal.SIGTERM
shows the following type error even we specify--unstable
flag on Deno 1.14.The command we used was
And the code we used was
We know that the API changes a bit (https://deno.com/blog/v1.14#changes-to-os-signals-apis) but string version didn't work on Windows so we need to stick on
Deno.Signal.SIGTERM
at least for now...