Skip to content
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

expose signal that killed the process #28

Open
SuperchupuDev opened this issue Aug 13, 2024 · 3 comments
Open

expose signal that killed the process #28

SuperchupuDev opened this issue Aug 13, 2024 · 3 comments

Comments

@SuperchupuDev
Copy link

No description provided.

@43081j
Copy link
Collaborator

43081j commented Aug 18, 2024

this may be as simple as introducing a getter for signalCode which is a pass through to process.signalCode

@SuperchupuDev
Copy link
Author

thatd be nice, but i just noticed i worded the feature request wrong 😅 i meant more of exposing it when spawn errors get thrown but that can work too

@43081j
Copy link
Collaborator

43081j commented Aug 19, 2024

when a spawn fails, it won't be a signal but will be a regular JS exception (e.g. if the command doesn't exist)

when the command does exist but exits for some reason, process.signalCode will tell you why

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants