Update body-parser to the latest version 🚀 #634
Merged
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.
Version 1.18.0 of body-parser just got published.
The version 1.18.0 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 body-parser.
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.
Commits
The new version differs by 32 commits.
adfa01c
1.18.0
0632e2f
Include the "type" property on all generated errors
b8f97cd
Include the "body" property on verify errors
c659e8a
tests: add test for err.body on json parse error
4e15325
tests: reorganize json error tests
5bd7ed5
tests: reorganize json strict option tests
3cb380b
tests: store server on mocha context instead of variable shadowing
29c8cd0
docs: document too many parameters error
7b9cb14
Use http-errors to set status code on errors
29a27f1
docs: fix typo in jsdoc comment
448dc57
Fix JSON strict violation error to match native parse error
87df7e6
tests: add leading whitespace strict json test
1841248
deps: raw-body@2.3.1
e666dbe
deps: http-errors@~1.6.2
c2a110a
deps: bytes@3.0.0
There are 32 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴