`yarn build` looking at last modified date about yarn.build HOT 2 CLOSED

Yep this is the tradeoff with last modified, it's faster but less resilient to edge cases than either per file hashing (computationally expensive) or IO events.

IIRC stashing files will remove them from the folder, but may not leave any trace. We might be able to cover this by looking for last modified per folder as well as per file.

I'm working on Gold the successor to yarn.build over at gold.build, I roughly planning an initial release towards the end of the year. I'm still merging fixes here, but I'm focussing most of my energy on Gold.

Tracking file changes is one of the areas where many problems and concerns come together. As a quick example you can only have so many file watchers (on some OS's) so you really want to have a program watching the IO events and relaying them to you, this is what watchman is built for.

But, just because you know a file has changed, doesn't mean its contents have meaningfully changed—thats what hashing can get you.

The scope of Gold is a bit bigger than this project, and this is one of the bigger problems I'm addressing with it.

from yarn.build.

Alright, thanks for your explanation!

from yarn.build.