Closed exlee closed 11 years ago
I'm not exactly sure what you mean by resource reload, but my auto-reload generally works through monster 15s sass compiles. So I don't think that is the issue.
However, the ws connection is fairly brittle overall, and it definitely does not survive things like restarting the watcher. Perhaps some auto-reconnect code ought to be added to the client side script.
Just a wild guess.
Unfortunately the only thing I'm sure of is that it fails with WS connection error (and then stops working completely).
I've started noticing it when working with Angular CoffeeScript/JADE template files (since I rarely work with stylesheets), with compile time around 800ms. Haven't got any issue when working with single JADE + CoffeeScript file with compile time being <200ms.
All sorts of things can go wrong with that ws connection that have nothing to do with brunch's implementation depending on your dev system, etc. #33 should solve it, so closing this for now. However, if you do figure out anything more specific about what's going wrong, please do post about it here.
I've found auto-reload to fail multiple times requiring browser refresh for it to work. The reason was the WS connection timeout.
I worked on multiple projects and I've noticed that this problem doesn't exist when the resource reload is short (100-200ms) and thus guess (I'm not sure about it) that it fails due to that.