.Net 6 Logging is not grouped anymore

[j-meds]

In .Net 3.1 and 5 the logging was grouped into one message. Now each line is an info message from VueCliMiddleWare, it's not good for debugging.

[SomeoneIsWorking]

For me, webpack progress is also written to logs as error even though there are no errors.

[andrew-smythe]

For me, webpack progress is also written to logs as error even though there are no errors.

This is happening for me too. In previous versions, these would not be logged as errors. Since I have a serilog sink on my project to send e-mails for logged errors, I get ~33 emails every time I fire up my project locally. I can reduce it to only one by using:

// vue.config.js
module.exports = {
    ...
    devServer: {
        progress: false,
    },
    ...
}

This just trims out the progress, which I still might want to see in the console output.

[SomeoneIsWorking]

I alleviated the problem by excluding the logs from Serilog with conditional

    private static bool IsCliLog(LogEvent logEvent)
    {
        return logEvent.Properties.TryGetValue("SourceContext", out var val) &&
               val is ScalarValue sv &&
               sv.Value is string svs &&
               svs == "VueCliMiddleware";
    }

But after upgrading to @vue/cli-service 5 the logs are not written as error anymore I think, because webpack version upgrade
I still keep this code to not include webpack logs in the log file

[j-meds]

Thanks for this, I'll try the upgrade first to see if it's resolved.

[gtbuchanan]

The error logging is occurring because Webpack logs diagnostics (including progress) to stderr by default. You can change the behavior of Webpack 5 by setting the stream option. Nonetheless, this doesn't help with the individual line logging.