Through my investigation in reverse engineering, I discovered that the culprit behind the display of the information is none other than `webpack-dev-server` itself. Unfortunately, there doesn't seem to be a built-in setting or option to modify this behavior. In order to address this issue, I resorted to implementing a workaround by extending the overlay's `showMessage()` method and removing the initial two lines that contain loader paths. Here is the snippet of the workaround I came up with:
const overlay = require('webpack-dev-server/client/overlay');
const show = overlay.showMessage;
overlay.showMessage = function (messages) {
const newMessages = messages.map(
msg => msg
.split('\n')
.slice(2)
.join('\n')
);
show(newMessages);
};