copy-webpack-plugin: Livereload is not triggered on file change

Bug report

Actual Behavior

Live reload is not triggered on file change

Expected Behavior

Live reload is triggered on file change

How Do We Reproduce?

git clone https://github.com/alan-agius4/copy-webpack-plugin-issue.git
yarn
yarn webpack-dev-server --open
mv asset/2.jpeg asset/1.jpeg

Notice that the image is not changed as live reload is not triggered.

  System:
    OS: macOS 11.6.4
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 4.29 GB / 64.00 GB
  Binaries:
    Node: 14.18.1 - ~/.nvm/versions/node/v14.18.1/bin/node
    Yarn: 1.22.17 - ~/.nvm/versions/node/v14.18.1/bin/yarn
    npm: 6.14.16 - ~/.nvm/versions/node/v14.18.1/bin/npm
  Browsers:
    Chrome: 99.0.4844.51
    Firefox: 91.6.0
    Safari: 15.3
  Packages:
    copy-webpack-plugin: ^10.2.4 => 10.2.4 
    webpack: ^5.70.0 => 5.70.0 
    webpack-cli: ^4.9.2 => 4.9.2 
    webpack-dev-server: ^4.7.4 => 4.7.4 

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 15 (13 by maintainers)

Most upvoted comments

@alan-agius4 oh, sorry, missed that, put in my TODO for tomorrow

@alan-agius4 Sorry for delay, looks like problem in webpack, because hash of compilation is the same, so dev server doesn’t reload page, I have two workarounds, but want to verify it is valid fixes, I will return to this today/tomorrow (waiting answer)

Looks like the user that reported the issue is also using Mac. https://github.com/angular/angular-cli/issues/22751#issuecomment-1059267890

@alan-agius4 I haven’t tried it yet, I’ve set it to my tasks, I can look tomorrow, just ask more information as possible