Logging to debug 500 Internal Server Error from Webpack Middleware #715

New Issue

fergalmoran · 2025-08-09T17:17:24Z

fergalmoran commented

2025-08-09 17:17:24 +00:00

Originally created by @jimmcslim on 5/28/2017

I have a webpack config that works fine from the command line, but throws a 500 (presumably from the Webpack middleware) whenever one of the entry points is accessed by the browser.

The Webpack middleware seems to be bit of a black-box at the moment, would it be possible to expose some of the Node.js instance's output? The 500 response returned empty content.

*Originally created by @jimmcslim on 5/28/2017* I have a webpack config that works fine from the command line, but throws a 500 (presumably from the Webpack middleware) whenever one of the entry points is accessed by the browser. The Webpack middleware seems to be bit of a black-box at the moment, would it be possible to expose some of the Node.js instance's output? The 500 response returned empty content.

fergalmoran closed this issue

2025-08-09 17:17:24 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/JavaScriptServices#715