零Rei

Thanks for your incredibly helpful feedback, Blaine and Dan! It should result in a much stronger next version of CLS! @dazld There are other use cases where the promises shims...

I have no objection to this as a feature, but there is little if no room for working on this in the npm roadmap for the foreseeable future, so it's...

Or, you know, using the `engines` field, because that's what it was designed for.

I have some comments on this, and I'd like to get the eyes of somebody who has a better grasp of Node's history with UNC paths to take a look...

@isaacs I haven't seen this happen on my machine since we released 1.4.15 with the fixes around locking. Given the VAST number of issues we see around this, though, I...

> Optimally it'd clean up any temp files on exit. Optimally, yes, but cleanup on exit in Node is not really very optimal (because you have no guarantees that anything...

It's tricky, because I've seen exit handlers fail to fire once there are more than a couple `process.on('exit')` listeners in some versions of Node.

Yeah, `beforeExit` is a possibility, but it'd still be best-effort, because `fs.writeStreamAtomic`'s primary consumer (not naming any names _cough_) is still going to need to support 0.10 after the release...