title: What causes this webpack code 2 error and how to solve it?
body: <p><em>Cannot even build in sidekick after a simple change</em></p>
  
  <p>I created a new Core/TS project in Sidekick, I built the app and developed some stuff, but later I changed the icon to a nicer one (which requires a new build, no HMR for this type of change obviously), now I cannot build my app (cloud build, because I don't have Android Studio).</p>
  
  <p>I checked the /main/assets/app/ and the icons were successfully changed there and they were existed.</p>
  
  <p>What is happening? How do I fix this big issue? My patience bottle with all these critical errors even after simple changes is getting <em>emptied</em>.</p>
  
  <p>I also tried "removing .cloud and folder directories", and clicking "clean cloud processes", adding "clean" option, etc...
  But none worked.</p>
  
  <hr>
  
  <p>I also updated the webpack.config.js file, with node_modules.bin\update-ns-webpack --configs
  The file got successfully updated, but still did <em>not</em> solve the problem and I still cannot build. </p>
  
  <p>Still after many hours cannot cloud build my app in sidekick. I also tried tns platform remove android, tns install, etc, etc... none worked out.</p>
  
  <p>this is the error message:</p>
  
  <pre><code>[00:00:18.521] [WARN]  Executing webpack failed with exit code 2.
  [00:00:18.681] [ERROR] clean-webpack-plugin: /mnt/storage/builds/_/af8fe992d35e76b54f5523261a83dac973ffc9ed/5.3.4/5.3.1/Spread/platforms/android/app/src/main/assets/app/**/* has been removed.
  Executing webpack failed with exit code 2.
  'Build failed with error code 2'.
  [19-06-10 19:13:56.767] Couldn't enable debugging for EP7333JKFA, Error: Couldn't enable debugging for EP7333JKFA
      at Errors.fail (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\common\errors.js:126:28)
      at Errors.failWithoutHelp (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\common\errors.js:136:21)
      at LiveSyncService.&lt;anonymous&gt; (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\services\livesync\livesync-service.js:253:30)
      at Generator.next (&lt;anonymous&gt;)
      at C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\services\livesync\livesync-service.js:13:71
      at new Promise (&lt;anonymous&gt;)
      at __awaiter (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\services\livesync\livesync-service.js:9:12)
      at LiveSyncService.enableDebuggingCoreWithoutWaitingCurrentAction (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\services\livesync\livesync-service.js:250:16)
      at LiveSyncService.enableDebuggingCoreWithoutWaitingCurrentAction (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\common\decorators.js:67:47)
      at LiveSyncService.&lt;anonymous&gt; (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\services\livesync\livesync-service.js:290:25)
      at Generator.next (&lt;anonymous&gt;)
      at fulfilled (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\services\livesync\livesync-service.js:10:58)
      at &lt;anonymous&gt;
      at process._tickCallback (internal/process/next_tick.js:188:7)
  OUTPUT 2
  </code></pre>
  
  <p>EDIT:
  SOLVED
  <a href="https://github.com/NativeScript/sidekick-feedback/issues/384#issuecomment-508028462" rel="nofollow noreferrer">https://github.com/NativeScript/sidekick-feedback/issues/384#issuecomment-508028462</a></p>