Real life purpose of emitting errors about BEM module

[qfox]

For now we have code for emitting errors about non existent BEM modules.

webpack-bem-loader/index.js

Lines 139 to 144 in e9c1640

	Object.keys(existsEntities).forEach(fileId => {
	// check if entity has no tech to resolve
	existsEntities[fileId] || errEntities[fileId].forEach(file => {
	this.emitError(`BEM module not found: ${file.path}`);
	});
	});

In real projects it looks like infinite noise that does not help.
At the same time emitError requires a special as an argument as passing there a string generates Critical errors inside Webpack itself.

ERROR in ./blocks/block-a/block-a.react.js
(Emitted value instead of an instance of Error) BEM module not found: ../block-b/block-b.css
 @ ./blocks/block-a/block-a.examples/index.react.js 21:26-59 21:71-104

Actually, there are 2 cases that we should fix here:

• Create an error object instead of string to pass it in emitError
• Reduce count of errors (to a zero if possible)

[Yeti-or]

I suppose this problem occurred after your project moved to webpack > 2
But it still valid one

[Yeti-or]

linked with: #22