Only touch if necessary

[svoop]

I'm trying to integrate rustywind into the build pipeline of a Bridgetown SSG site. However, Bridgetown uses live reloads, so whenever rustywind touches the source files, it triggers a reload which triggers rustywind, which touches the source files... you get the rap.

Checking with stat, rustywind in fact touches all files even if the existing file and the reordered files are identical.

Would it be possible to only write files if they have to be written and to skip them if nothing has changed?

(In case this is less efficient than always writing, maybe add a --force argument: --write only writes if necessary and --write --force always writes.)

[praveenperera]

Thanks, this was a huge oversight on my part. Fixing this should speed up RustyWind.

Opened a PR, let me know if you can build it locally and test it.

[svoop]

Cool, thanks for the PR! I'd be happy to test. For Bridgetown, these tools are installed using yarn. Bit out of my turf, though: Is there a way I can tell yarn to take a particular branch, in this case avoid-write?

[praveenperera]

@svoop released in v0.21.0

[svoop]

@praveenperera Works like a charm! The endless loop is now down to two runs and the rebuild is quite a bit faster. To get it down to just one run, the way rustywind is called has to be changed, but that's another problem on the Bridgetown end. Really cool such a quick fix, Christmas is a bit early this year 😉 Thanks a bunch and happy holidays!