npm run watch deletes clientlib-site/css & /js in Archetype 39

### Expected Behaviour
Running `npm run watch`, it should deploy a new version of the frontend css/js to the author instance.

### Actual Behaviour
Running `npm run watch`, that is `"watch": "npm-run-all --parallel start chokidar aemsyncro"`, it deletes /apps/{package id}/clientlibs/clientlib-site/css/ and /js/ from the running author instance.

To temporarily resolve the issue, I run `webpack-dev-server -- ./webpack.dev.js --env writeToDisk & chokidar -c \"clientlib\" ./dist & aemsync -w ../ui.apps/src/main/content` and this re-deploys a new version of the css/js.

### Reproduce Scenario (including but not limited to)

#### Steps to Reproduce

#### Platform and Version
Archetype ver 39

#### Sample Code that illustrates the problem

#### Logs taken while reproducing problem

Read the npm watch script and webpack.dev.js, then reproduce the issue with Archetype 39 against the running author instance. Check the clientlib and dist synchronization behavior; done means npm run watch deploys the frontend CSS and JavaScript without deleting clientlib-site/css or clientlib-site/js.

Written by the indexing model from the issue text.