Skip to content

docs: note that req.body may be undefined in v2 #752

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Hashim1999164 wants to merge 1 commit into
base: master
Choose a base branch
from
Open

docs: note that req.body may be undefined in v2 #752

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,12 @@ The `bodyParser` object exposes various factories to create middlewares. All
middlewares will populate the `req.body` property with the parsed body when
the `Content-Type` request header matches the `type` option.

**Note** As of v2, `req.body` is left `undefined` when no body is parsed (for
example an empty body or a non-matching `Content-Type`). In v1, `req.body` was
always initialized to `{}`. Code that assumes `req.body` is always an object
should use optional chaining (for example `req.body?.username`) or set a
default.

The various errors returned by this module are described in the
[errors section](#errors).

Expand Down