Open nothingrandom opened 10 months ago
I have this issue as well. It happens with TypeScript, not sure if it happens with JSX as well.
here is the link in webpack's docs. Apparently the err object does not contain the error so this repo needs to be updated.
webpack(config, (err, stats) => {
if (err || stats.hasErrors()) {
console.log('stats:', stats.toString({ colors: true }));
// ...
}
// Done processing
});
Created a PR above, hopefully he approves of it. There is an attached screenshot for the failed build error.
If there is a path error (eg change a directory name in a clean build) or a Typescript error running
npm run build
will fail, completely silently, with a success code.Meanwhile,
npm run start
will provide some form of erroring.Would be really useful (basically essential) for pipelines to start getting
build
to error properly and provideexit 1