fix: external files are not livesynced

In case you have external files set in the webpack.config.js (or resources copied with CopyWebpackPlugin), the `tns run ...` command does not LiveSync them to device. Webpack compilation is triggered, but as the emitted files are not hot updates, the hot update hash of the compilation is the same as the previous one. In this case CLI decides there's nothing to sync.
To fix this extend the check in webpack-compiler-service to be based not only on the comparison between previous and current hash, but on the emitted files as well - if there are files which are not hot updates, continue the execution even if the previous and current hash are the same. That's exactly the case with externals.

Author: rosen-vladimirov

lib/services/webpack/webpack-compiler-service.ts

@@ -49,11 +49,7 @@ export class WebpackCompilerService extends EventEmitter implements IWebpackComp
 							return;
 						}
 
-						// the hash of the compilation is the same as the previous one
-						if (this.expectedHashes[platformData.platformNameLowerCase] === message.hash) {
-							return;
-						}
-
+						const previousHash = this.expectedHashes[platformData.platformNameLowerCase];
 						let result;
 
 						if (prepareData.hmr) {
@@ -78,6 +74,12 @@ export class WebpackCompilerService extends EventEmitter implements IWebpackComp
 						};
 
 						this.$logger.trace("Generated data from webpack message:", data);
+
+						// the hash of the compilation is the same as the previous one and there are only hot updates produced
+						if (data.hasOnlyHotUpdateFiles && previousHash === message.hash) {
+							return;
+						}
+
 						if (data.files.length) {
 							this.emit(WEBPACK_COMPILATION_COMPLETE, data);
 						}