Update hapi-auth-jwt2 to version 7.2.2 🚀 #18
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello lovely humans,
hapi-auth-jwt2 just published its new version 7.2.2.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of hapi-auth-jwt2.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
The new version differs by 7 commits .
f55e939
lint code using goodparts see: As part of improving code-readability can we also conform to ESLint (e.g: goodparts) ? dwyl/hapi-auth-jwt2#211 -> 100% backward compatible no features added/removed.
7e0ae62
lint code using goodparts see: As part of improving code-readability can we also conform to ESLint (e.g: goodparts) ? dwyl/hapi-auth-jwt2#211 -> 100% backward compatible no features added/removed.
a3300cc
Merge pull request #213 from dwyl/refactor-to-goodparts
6eac431
include "goodparts" (javascript styleguide) badge in readme. see: https://github.com/dwyl/goodparts
2ec49ef
update order of commands in pre-commit in package.json (includes linting) #211
eb3d07d
linting of lib/index.js (refactoring to use goodparts) complete. no changes to tests. improvement in execution time! fixes As part of improving code-readability can we also conform to ESLint (e.g: goodparts) ? dwyl/hapi-auth-jwt2#211
03ddcaf
[WiP] add goodparts and start linting /lib see: As part of improving code-readability can we also conform to ESLint (e.g: goodparts) ? dwyl/hapi-auth-jwt2#211
See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade