-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🙏🏻 [feat/req] Implement signal handlers for Windows #9995
Comments
There is a stalled partial implementation (Windows CTRL-C/CTRL-BREAK (SIGINT/SIGBREAK) signal handler). related |
😃 |
When testing with a generated prisma client(without windows) it seems like the following signals break on windows when adding the signal listeners: SIGUSR2, SIGINT, SIGTERM, beforeExit, exit. this is when using createrequire via "node:module" and importing the generated client
Should similar functionality to nodejs be made for these signals? |
I encountered this error on deno 1.39.1. import puppeteer from 'npm:puppeteer-core@21.7.0'
await puppeteer.launch({
executablePath: 'chrome'
})
This works: import puppeteer from 'npm:puppeteer-core@21.7.0'
await puppeteer.launch({
executablePath: 'chrome'
, handleSIGHUP: false
, handleSIGTERM: false
}) |
The |
Currently, all the available signal handling API throw "unimplemented" errors for Windows platforms.
It would be great to have cross-platform signal handling along the lines of NodeJS Process Signal Events...
The text was updated successfully, but these errors were encountered: