Philipp Dunkel

Hi all, we have every intention to publish the polyfill to npm and make it available. Right now we are waiting to stabilize the spec a bit more, which I...

@zloirock where in the code-tree would you want me to place it, and how would you want it exposed? Contrary to the other stuff this is meant as a *builtin...

However since there are Instant.fromEpochMilliseconds() and Instant.fromEpochSeconds() the polyfill we have can be used without BigInt support. Literally the only bits that can’t be polyfilled are: Instant constructor Instant.fromEpochNanoseconds() and...

Is it possible that it's reporting an *change of atime*?

The latest libuv does use fsevents under the hood these days. This was an effort undertaken by libuv a while back after chatting about moving fsevents into node core at...

@remy *chokidar* is basically a wrapper around `fs.watch` and *fsevents*. So in terms of that modern *libuv* provides a `fs.watch` that eliminates the shortcomings of earlier versions and obviates chokidar.

I think that's a good idea.

Chokidar is code by evolution and could benefit from cleanup & refactor. As part of that chokidar could be subsumed into core. FSEvents was also code by evolution. Except it...

I guess we come at it from a different perspective. My main use-case has always been micro-service apis. Most of those run on anything but MacOs. If I were to...

There seem to be 2 issues here. 1) the *.node* binary isn’t included in the binary, so it won’t be found when searching for it; and 2) even if you...