Update passport-jwt to the latest version 🚀

[greenkeeper[bot]]

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 4.0.0 of passport-jwt was just published.

Dependency	passport-jwt
Current Version	3.0.1
Type	dependency

The version 4.0.0 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 passport-jwt.

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.

---

Commits

The new version differs by 5 commits.

• 8f543a9 Update version to 4.0.0
• f381cea Updating migration guide for 4.0.0
• 5497660 Update jsonwebtoken dependency to latest.
• 685fffe Move supporters up a little higher in README
• d2d950e Remove codesponsor.io link

See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper bot :palm_tree:

[kkkrist]

Could you please cut a new release and publish to npm? Current \@latest on npm still depends on passport-jwt ^3.0.0 which will pull in a vulnerable version of hapijs/hoek, see https://nvd.nist.gov/vuln/detail/CVE-2018-3728

Thanks!

[daffl]

Done as v2.0.1