Expose fs.Stats constructor

[billiegoose]

I need to transport some fs.Stats objects across JS domains, by serializing them and deserializing them. I see there is a nifty .toBuffer() instance method and a .fromBuffer() static method to do this! But I don't see how to get ahold of the static method. The Stats constructor isn't exposed? In Node, I can do this:

> let s = new (require('fs').Stats)
undefined
> s
Stats {
  dev: undefined,
  mode: undefined,
  nlink: undefined,
  uid: undefined,
  gid: undefined,
  rdev: undefined,
  blksize: undefined,
  ino: undefined,
  size: undefined,
  blocks: undefined,
  atimeMs: undefined,
  mtimeMs: undefined,
  ctimeMs: undefined,
  birthtimeMs: undefined,
  atime: Invalid Date,
  mtime: Invalid Date,
  ctime: Invalid Date,
  birthtime: Invalid Date }

Could you add Stats as a public static member of fs (to match the Node API)?

[jvilk]

Ah, this is an oversight. It's exposed on the FS class, but not on the node_fs singleton.

A simple fix is to expose it on that singleton _fsMock object in node_fs.