This issue has been automatically marked as idle and stale because it hasn't had any recent activity. It will be automtically closed if no further activity occurs. If you think this is wrong, or the problem still persists, just pop a reply in the comments and @remy will (try!) to follow up.
Thank you for contributing <3

This is still an issue. The work-around gets the job done, but could also falsely trigger a re-start if any other YAML files are in the watched directories.

ACK - this is actually a bug, though not entirely apparent. If you run nodemon in the src directory and ask it to run as nodemon -w ./openapi.yaml -w . ./server.ts it works, but if you're watching in a sub-directory it doesn't - as you're experiencing.

I'm trying to work on a fix for this.

I wrote a fix last night but it's not fully passing tests (but I think those tests need to be updated).

I've published a dev build if you want to try it out though - if you install using npm install nodemon@dev you should be able to test it out.

Tried it and it worked. Will watch for an updated release.

This issue has been automatically marked as idle and stale because it hasn't had any recent activity. It will be automtically closed if no further activity occurs. If you think this is wrong, or the problem still persists, just pop a reply in the comments and @remy will (try!) to follow up.
Thank you for contributing <3

Commenting to keep this alive. Any estimate on the next release?

I'm still trying to scrape the time to get the tests to pass (I've marked as not-stale to prevent the bot from closing). The code change is there, but there's a lot of tests that fail (in the match logic) due to the change, and I'm trying to work out which are false negatives and which are real. Definitely going in soon…ish!

That's going up in the latest release now 👍

🎉 This issue has been resolved in version 3.1.6 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀