Open aronmgv opened 8 years ago
Same setup, same result. I can confirm this. When I run this on macOS it works fine.
npm 3.9.1 node v4.2.6
Edit: doesn't work on macOS either.
Edit: I found out i've set the bs.stream before the gulp.dest. So ignore this post :)
Issue details
Browser-sync injects old css version into browser (chrome and ff tested).
I have disabled caching in chrome (devtools->options->disable cache when devtools is opened)
Hard reload with emptying cache reflects most recent changes.
Steps to reproduce/test case
I made a change to the less file -> less compiled to css -> see injected css file into the chrome, but it is not the one I have saved on disk - it is non existent anymore and it is being injected for some period of time..
I repeat this process and observe that in order to get the actual changes injected into the chrome first it injects all change history of the css file.. so I do a white space changes to force it further.. (I see in chrome all versions of the css file which was injected.. and e.g. first 5 have the original css file, then I start seeing my changes)
I repeated the process editing just from the notepad.. same results.
Please specify which version of Browsersync, node and npm you're running
Affected platforms
Browsersync use-case
for all other use-cases, (gulp, grunt etc), please show us exactly how you're using Browsersync