"Build failed with errors" message instead of webpack cause

[Toilal]

When webpack build fails (npm build), it displays "Build failed with errors" without any other explanation.

Problem is that this piece of code hide actual errors.

webpack/template/build/build.js

Lines 22 to 28 in ecd68c4

	process.stdout.write(stats.toString({
	colors: true,
	modules: false,
	children: false,
	chunks: false,
	chunkModules: false
	}) + '\n\n')

If is set this to toString({color: true}), errors are displayed with other informations.

[LinusBorg]

On what kind of errors does this happen?

I tried:

• a syntax error wiht eslint enabled: shows eslint errors
• as syntax error with eslint disabled: shows error with highlighted code-snippet.
• a from path on an import: shows "module not found ..." error

Please provide more information.

[Toilal]

import { Vue } from 'vue/types/vue' instead of import vue from 'vue'

[Toilal]

Sorry, I forgot one important thing ! The error is caused by ts-loader (i'm running typescript).

[LinusBorg]

[LinusBorg]

Sorry, I forgot one important thing ! The error is caused by ts-loader (i'm running typescript).

Not an unimportant detail ^^

[LinusBorg]

Please provide a repository with a reproduction, I won't build one myself.

[Toilal]

https://github.com/pragmasphere/vue-tree

It's fixed in this repository, but you revert those lines

https://github.com/pragmasphere/vue-tree/blob/2302c9b18b7298a0e83ad18f43d2f212bb487078/build/build.js#L22-L24

[LinusBorg]

Thanks. Seems ts-loader is a weird beast. In webpack 1, it even made webpack exit with code 0 on a compile error (TypeStrong/ts-loader#108), so getting errors out of ts-loader seems to not be that easy :-P

So I played around a little and found that removing children: false is enough to make the error appear again.

The thing is that this alone makes the output quite verbose on a successful build. and since this template is not laid out for typescript yet, I would hesitate to make the output verbose for everyone just to accomodate those who implement typescript into that template on their own.

So my suggetion would be the following:

1. Add a comment in build.js to tip off people using typescript how to fix it.
2. If /when we make typescript an option for the template, with e.g. Minimal TypeScript support option added #797, we can make this option change depending on wether typescript was added or not.

Does that sound sensible to you?

[Toilal]

I think the comment would be ok for now.

In fact I realised later the problem was maybe related to ts-loader, so let's close this one, no problem. thanks :)