Update dependency body-parser to v2 - autoclosed #76
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.



This PR contains the following updates:
^1.15.1->^2.0.0By merging this PR, the issue #21 will be automatically resolved and closed:
Release Notes
expressjs/body-parser (body-parser)
v2.2.1Compare Source
=========================
encodingExistsby using prototype-less objectsv2.2.0Compare Source
=========================
v2.1.0Compare Source
=========================
v2.0.2Compare Source
=========================
unpipepackage and use nativeunpipe()methodv2.0.1Compare Source
=========================
extendedtofalsev2.0.0Compare Source
=========================
Breaking Changes
req.bodyis no longer always initialized to{}undefinedunless a body is parsedbodyParser()combination middlewareas released, this is not the case, fixed in 2.0.1urlencodedparser now defaultsextendedtofalseurlencodedsimple parser now usesqsmodule instead ofquerystringmoduleFeatures
on-finishedto determine when body readDependencies
v1.20.3Compare Source
===================
depthoption to customize the depth level in the parserdepthlevel for parsing URL-encoded data is now32(previously wasInfinity)v1.20.2Compare Source
===================
v1.20.1Compare Source
===================
v1.20.0Compare Source
===================
strictevalusage withFunctionconstructorprocessto check for listenersv1.19.2Compare Source
===================
__proto__keysv1.19.1Compare Source
===================
v1.19.0Compare Source
===================
pb) supportthrowon invalid type