Au build --watch does not refresh the changes

1

Hi
Today when I execute au build --watch and I make changes after save I go to the Chrome to Refresh the changes but these are not refreshed and I have to execute au build --watch again.

Any idea please?

regards

1 Like
2

chrome may be caching the bundle, in chrome try going to developer tools > network and check ‘disable cache’, or try ctrl+f5 (cmd+r on mac) to force reload

3 Likes
3

Hi

The problem is that au build --watch some times when I save the changes does not generate the new bundle. And I have to rebuild it. Sometimes yes sometimes no.

Thanks

1 Like
4

Are you using docker or a network mounted disk?

1 Like
5

I’m working in the local disk of my Mac mini

1 Like
6

Are you using webpack or requirejs/systemjs? Any other special setup? I am curious to reproduce the issue.

1 Like
7

WebPack and this is something random. Sometimes the build does not, and you never know when it’s going to be good

1 Like
8

It’s probably some webpack bug, unlikely related to aurelia. You might be able to find something here https://github.com/webpack/watchpack/issues

1 Like
9

Perhaps you can tell more about the nature of the changes? My experience is that e.g. Interface changes need a new au run --watch.

1 Like
10

I had the same issue, but found that fs.inotify.max_user_watches was exceeded. Increasing it solved my issues. See https://github.com/webpack/webpack/issues/1281 and https://support.code42.com/CrashPlan/4/Troubleshooting/Linux_real-time_file_watching_errors

1 Like
11

FWIW, looked at that. max_user_watches isn’t being exceeded. So, this didn’t work for me.

1 Like