Update nodemon to the latest version 🚀

[greenkeeper]

Version 1.17.5 of nodemon was just published.

Dependency	nodemon
Current Version	1.17.2
Type	devDependency

The version 1.17.5 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of nodemon.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

---

Release Notes

v1.17.5

1.17.5 (2018-05-23)

Bug Fixes

• in watch, use fully filtered ignore rules (b3fc3a9), closes #1348

Commits

The new version differs by 10 commits.

• b3fc3a9 fix: in watch, use fully filtered ignore rules
• ff79835 chore: update stalebot
• ee2aac1 fix: support env.SUPPRESS_SUPPORT (#1334)
• 58b82f2 fix: increase perf of watching large file count
• f616258 fix: {{filename}} is only replaced once
• 97f8d0a fix: node_modules watched off relative path (#1328)
• 9bbc219 fix: only hook SIGINT on boot - not at require
• d53a244 chore: mildly reduce npm package size
• 6925494 docs: use consistent ext example
• aa18c80 fix: don't throw when required in the repl

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper bot 🌴

[googlebot]

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

[googlebot]

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

[googlebot]

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

[googlebot]

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)