3 ms·

I made a batch file to run npm 3 times when they had a bug in assuming atomic file actions. They have fixed this bug and the latest versions of npm. It only hap

by sosuke 11y ago

I made a batch file to run npm 3 times when they had a bug in assuming atomic file actions. They have fixed this bug and the latest versions of npm. It only happened on cloud servers for me and it was assumed a result of slow IO highlighting the bug.

tbrock 11y ago
Eh I'm not sure that is the same problem. We could reproduce this behavior on everything from MacBook Airs to honking i7s with fast SSDs as well as the cloud.
- jt2190 11y ago
  The case you describe definitely sounds "broken" to me. I think it'd be very, very helpful if you could provide your test cases to the npm project.
  - tbrock 11y ago
    It's already well documented here https://github.com/npm/npm/issues/10727 https://github.com/npm/npm/issues/10727