Yarn build --debug --livereload --watch causes assets to become increasingly nested upon rebuild

[conoremclaughlin]

Thanks again for the preset and all the help to the community!

What is the issue?
Upon rebuilding, webpack will recursively nest the assets folder with each rebuild. This causes livereload to break for images and newer JS files.

Expected behavior
Everything should be rebuilt and remain within the top-level build/ directory so live reloading works properly and doesn't point at the wrong asset files. In the case of copying over images or other static assets, after the first rebuild, the browser will throw an error stating it is unable to find the specified assets in the manifest.

Steps to reproduce

1. Check out this repo
2. yarn install
3. yarn build --debug --livereload --watch
4. Edit any source file watched for a meaningful change
5. Check build/ directory to see the nested folder structure

Will be digging more into the cause. Thanks for any help :)

[crimx]

This may indicate building failures. What happen if you run yarn build?

[conoremclaughlin]

yarn build and yarn build --debug (--livereload)? create the right output and the build succeeds. It's on the second rebuild while watching and thereafter that the recursive nesting structure is created. I suspect this is a problem with Webpack ^4 and my MacOSX environment. The situation is tricky with Webpack 5's release. I'll try downgrading later and see if that helps.

Environment

webpack: 4.44.1
webpack-cli: 3.3.12
MacOSX: Catalina 10.15.7 

[crimx]

This is because the old builds for each browser didn't get clean-up. I'll fix this when I have time. Thanks again for the input!