When emitting "error" and "compilation-error" events on the stream, underlying errors reported as stats.errors by Webpack were joined without newlines. This could lead to error messages like these (taken from the build output of a project that uses webpack-stream and ts-loader):
[tsl] ERROR in D:\frontend\app\views\SampleView.ts(8,2)
TS2564: Property '_parentEntity' has no initializer and is not definitely assigned in the constructor../app/views/SampleView.ts
[tsl] ERROR in D:\frontend\...
Note the absence of a newline before ../app/views/SampleView.ts.
In this commit:
Individual error messages are joined with \n.
A test('error formatting') is added that checks error formatting using a fake Webpack loader producing some errors (test/fake-error-loader.js).
shama
commented
6 years ago
When emitting "error" and "compilation-error" events on the stream, underlying errors reported as
stats.errorsby Webpack were joined without newlines. This could lead to error messages like these (taken from the build output of a project that useswebpack-streamandts-loader):Note the absence of a newline before
../app/views/SampleView.ts.In this commit:
\n.test('error formatting')is added that checks error formatting using a fake Webpack loader producing some errors (test/fake-error-loader.js).