Deleting large non-binary file takes extremely long time

[bdukes]

We have a generator which includes a local copy of Yarn (the result of yarn set version ^1), which is a 5MB JavaScript file. After updating this file to the latest version, the delete of the file is taking a very long time (close to an hour). After debugging the process, it looks like the conflict detection is looping through the file to calculate a diff.

Is it possible to short-circuit that conflict check for deletions, or configuration I could do to skip it for specific files?

[mshima]

Can't you directly copy to the real path at end step?

[bdukes]

So instead of using this.fs.delete in writing(), just use fs.unlink directly in end()? That does seem like it would be a workable workaround.

[mshima]

Exactly.
The api to ignore conflicts can be done, and should be kind of easy, it would use transformStream.