-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Running required nodemon multiple times #286
Comments
I'm running into this issue myself. (I'm trying to run multiple instances via Gulp.) I think returning new instances makes the most sense although I can see how that would be a big refactor and definitely API breaking. Still, I think that'd be the right thing to do. I'm working on getting familiar with the codebase now to see how much work it'd be. |
a whole year passed and issue is not resolved ^^ |
For my project, I think we ended up using https://github.com/substack/watchify or the built-in Gulp watch features. |
@remy Is there any plan to add this feature? |
No, not without a PR. |
We've been using concurrently together with |
If you're using gulp to launch nodemon you can use node-multi-process to launch multiple instances. See example here ColemanGariety/gulp-nodemon#6 (comment) |
Will fix this ColemanGariety/gulp-nodemon#6
Currently if you require nodemon, it's a static, so you can require multiple times (or rather - it makes no difference).
I'm not sure what to do right now, whether nodemon should return a new instance (which is potentially a lot of work...possibly) or whether nodemon internally tracks multiple monitors (which is potentially messy).
Would love any community input, ideas and help to code this up if possible.
The text was updated successfully, but these errors were encountered: