body-parser
body-parser copied to clipboard
expressjs
Node.js body parsing middleware
Hi, A while ago I developed a web app to replace an old cgi-bin script from the nineties, which means that it had to assume that POST requests with a...
Integers larger than 53 bits are valid JSON, but when parsed by JSON.parse they get truncated down to 53 bits and lose a few least significant digits. We have 64...
We are looking for a way to pass custom options to the urlencoded parser, this has previously been denied due to `qs` being deprecated https://github.com/expressjs/body-parser/pull/98. Would this solution to allow...
Working draft: http://www.w3.org/TR/html-json-forms/ Thoughts from `qs`: https://github.com/hapijs/qs/issues/63 This support may not even be called `extended: true` within the `urlencoded` parser; it may move to be an option of the JSON...
In a project I work we use body-parser and mysql2 as dependencies. We are running a very common combination of prisma+mysql2 / expressjs+bodyparser in vercel, and every bundle kb is...
Allow user to specify a function to run on the parsed output. This function gets the req and res as does the normal parsing middlewares but operates on the parsed...
It would be nice if the `json` middleware could support [ndjson](http://ndjson.org/) as well. e.g, something like this as input: ``` { "id": 1, "message": "hello" } { "id": 2, "message":...
Hi! v6.11.1 and v6.11.2 has some fixes: [Fix] parse: Fix parsing when the global Object prototype is frozen [Fix] stringify: encode comma values more consistently https://github.com/ljharb/qs/blob/main/CHANGELOG.md#6112
The json middleware does not parse results as json if the content type is anything but `application/json`, I would expect it to also work on content types like `application/ld+json`. For...
This PR fixes [nyc](https://github.com/istanbuljs/nyc) version to 14.1.1 when running tests in node 8 or node 9. `nyc 15.x `requires a `yargs` package version that requires node >=10. I've also added...
