-
Notifications
You must be signed in to change notification settings - Fork 51
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
PID-tracking / kill-signal support #20
Labels
Comments
I think this would be a good addition to chokidar-cli and I'm willing to merge a PR if someone wants to implement this feature. |
4 tasks
If it helps anyone, nodemon --watch . --exec "eslint --cache ." |
I achieved it by adding few scripts in package.json "scripts": {
"start": "node myapp.js",
"kill": "pkill -f myapp.js",
"restart": "npm run kill; npm run start;",
"watch": "./node_modules/.bin/chokidar --initial '**/*.js' -c 'npm run restart'"
} Now just run: npm run watch |
PING here |
PR welcome for this feature 👍 |
There is an old PR with this implemented #31 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
So, this might be a little out-of-scope, but I figured I'd point out it's a desirous feature:
It'd be nice if
chokidar
could automatically kill (or better yet, send an arbitrary single to) the previous invocation when it starts a new one. (For instance, when a test-file is changed before a long-running test suite is complete; or in my particular use-case, allowing me to wrap the desired command inless
and wanting theless
-instance to be killed whenchokidar
invokes a new instance of the command.)The text was updated successfully, but these errors were encountered: