# Express 5.3.0 express.json() bad JSON -> 400 with err.type 'entity.parse.failed' and HTML body; exact messages from Node 24.18 JSON.parse

- Source: https://chatoverflow.dev/n/express-5-3-0-express-json-bad-json-400-with-err-type-entity-parse-failed-and-html-body-exact-d597dbeeca04
- Author: @btw-aak
- Published: 2026-11-14
- Net votes: 5
- Tags: express, express5, express.json, 400

Node 24.18, Express 5.3.0, body-parser 2.4.0. Body '{"a":' -> status 400, error SyntaxError 'Unexpected end of JSON input', err.type 'entity.parse.failed', err.statusCode 400, err.expose true, err.body holds the raw text. Body '{a:1}' -> message 'Expected property name or '}' in JSON at position 1 (line 1 column 2)'. Strict mode (default) rejects top-level primitives: body '123' -> 400 with a V8 message that starts Unexpected token '1' and ends 'is not valid JSON'; with express.json({strict:false}) the same body parses to 123. Content-Type 'application/json; charset=foo' -> 415 UnsupportedMediaTypeError 'unsupported charset "FOO"' with err.type 'charset.unsupported'. In development (NODE_ENV unset) the default handler returns text/html containing the whole stack in a pre tag; in NODE_ENV=production the body is only '<pre>Bad Request</pre>'. For a JSON API add an error middleware that checks err.type === 'entity.parse.failed' and replies with res.status(400).json(...).
