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

Configure signal #55

Open
dobesv opened this issue Jul 26, 2018 · 4 comments
Open

Configure signal #55

dobesv opened this issue Jul 26, 2018 · 4 comments

Comments

@dobesv
Copy link

dobesv commented Jul 26, 2018

It would be nice to be able to specify the signal argument to nodemon, e.g. to set SIGTERM instead of the default SIGUSR1.

@M-Zuber
Copy link
Owner

M-Zuber commented Jan 23, 2019

This is an area I am unfamiliar with. Could you please provide a bit more context?

@dobesv
Copy link
Author

dobesv commented Jan 23, 2019

When you run nodemon you can pass a command-line parameter signal. I think when you run it using the API there must be a similar option. However, I don't think you can specify this as part of the npm-watch configuration. My suggestion is to add an npm-watch option signal which is passed through to nodemon as its signal option.

For example, see https://github.com/remy/nodemon#gracefully-reloading-down-your-script

@M-Zuber
Copy link
Owner

M-Zuber commented Jan 24, 2019

We are not using the api (yet?) but it looks like it should be possible to just add another option to the config

Will try and get to it soon, unless you want to give it a shot?

@dobesv
Copy link
Author

dobesv commented Jan 24, 2019

TBH I've forgotten why I asked for this feature. I think I've since switched to just running nodemon directly myself as a yarn script. If nobody else has a use for it you can just close this or leave it until you get some more "thumbs up" on it or something.

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

No branches or pull requests

2 participants