Express: How come only bodyParser.json is exposed?
This module depends on body-parser and exposes bodyParser.json. However, if someone wanted to get the pure text result of the output, or use another method from body-parser, they'd have to install it themselves. Why not just expose all of the functions and save the user an extra install? Or not expose anything, and make the module lighter?
vityavv
All 2 comments
I think the general idea was to remove all these originally, but the json one was brought back. I looked quickly for the old conversations but it was too long ago for me to remember what to look for.
I do think, if the choice is to include any, then all should be exposed. But maybe there was some question about this someone else would remember better.
wesleytodd
on 19 Jun 2018
The others are being exposed in Express 4.17. Follow the release and what it includes in #3778
dougwilson
on 27 Oct 2018
Related issues
Domiii
路
3Comments
extensionsapp
路
3Comments
cuni0716
路
3Comments
jefflage
路
4Comments
snowdream
路
3Comments
Most helpful comment
I think the general idea was to remove all these originally, but the
jsonone was brought back. I looked quickly for the old conversations but it was too long ago for me to remember what to look for.I do think, if the choice is to include any, then all should be exposed. But maybe there was some question about this someone else would remember better.