Nodemon: Running required nodemon multiple times

[remy]

Will fix this https://github.com/JacksonGariety/gulp-nodemon/issues/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.

[darzu]

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.

[let4be]

a whole year passed and issue is not resolved ^^
The same problem, any workaround?

[darzu]

For my project, I think we ended up using https://github.com/substack/watchify or the built-in Gulp watch features.

[ratson]

@remy Is there any plan to add this feature?

[remy]

No, not without a PR.

[simison]

We've been using concurrently together with gulp-nodemon: https://github.com/Trustroots/trustroots/blob/master/package.json#L22

[mjy78]

If you're using gulp to launch nodemon you can use node-multi-process to launch multiple instances. See example here https://github.com/JacksonGariety/gulp-nodemon/issues/6#issuecomment-330788506