ext-webpack-plugin swallows underlying errors

[shieldsjared]

Not sure when this change occurred, but when using the ExtWebpackPlugin, any error that occurs after processing of the plugin itself, the underlying error is swallowed and the user has no visibility into the problem.

Simple way to replicate this:

1. Launch anything on port 8080 for example (e.g. make sure the port is in use)
2. Launch webpack w/ this plugin, and use port 8080... the process will start and then die and give you NO indication as to what hte problem is...

Offending code is somewhere in this block

ext-allshared/packages/ext-webpack-plugin/src/index.js

Lines 22 to 37 in 3afcf36

	var v = [`exit`, `SIGINT`, `SIGUSR1`, `SIGUSR2`, `uncaughtException`, `SIGTERM`]
	v.forEach(eventType => {
	process.on(eventType, function(eventType){
	if (me.vars.child != null) {
	console.log('\nnode process and sencha cmd process ended')
	me.vars.child.kill();
	me.vars.child = null;
	}
	else {
	if (eventType != 0) {
	console.log('\nnode process ended')
	}
	}
	process.exit();
	});
	})

please fix this! We lose countless hours troubleshooting by trial and error since we cant see the underlying problems when performing other webpack configurations.

With the plugin swallowing anything, this is a sample of all you see with vebose enabled:

XXXXXXXX@XXXXXXXX MINGW64 /d/src/XXXXXXX (feature-21377-webpack)
$ npm run watch

> XXXXXXX@1.0.0 watch D:\src\XXXXXXX 
> webpack-dev-server --env.browser=no --env.verbose=yes --progress --color

-verbose: FUNCTION _constructor
-verbose: pluginName - ext-webpack-plugin
-verbose: app - i [ext]: 
i [ext]: ext-webpack-plugin v7.2.0, Ext JS v7.2.0 Commercial Edition, Sencha Cmd v7.2.0.84, webpack v4.39.3, react v16.12.0
i [ext]: Starting development build for react
-verbose: Building for development, treeshake is no, intellishake is yes
-verbose: FUNCTION _thisCompilation
-verbose: options.script:
-verbose: buildstep: 1 of 1
-verbose: FUNCTION _compilation
10% building 1/1 modules 0 active
node process ended