chore: add .nvmrc

[joelmukuthu]

I just went full-circle from another project before finding #18 :)

I set it to v6 instead of v7 as 6 is an LTS version.

[coveralls]

Coverage remained the same at 90.141% when pulling e7659ae on chore/nvmrc into 9e61f9d on master.

[gustavnikolaj]

Thanks :-)

I am not sure what the future of this module will be though. I personally don't depend on anywhere critical enough to have me pick up maintenance of the mock-fs-fork that we are running. Just a headsup, before you tie yourself to a sinking ship 🚢

I like the idea of this module, but lately I've found myself just using a mix of fixture folders and tmp directories. It is a bit more manual labor and a bit more verbose, but it still feels like less effort than getting this up to date and keep it there :-)

---

For the record, the problem with mock-fs is that it basically carries around a modified version of fs.js from node core per version of node. So there is going to be a non trivial amount of work involved staying up to date with their changes. I'm no longer convinced that this is worth that effort. But it's a shame to give up a nice abstraction like this :-)

[gustavnikolaj]

I'd probably bet my money on fileception going forward, but that probably has the exact same issues at the moment. https://github.com/papandreou/fileception

[joelmukuthu]

ping @gustavnikolaj @papandreou :)

[joelmukuthu]

Oops, sorry. I pinged before first attempting to reload my browser tab.

@gustavnikolaj that's alright and thanks for the info. I just ran into the issue while trying to run CI on newer node versions on unexpected-knex. All the same I agree that the effort in trying to mock out fs is probably not justifiable, and in ensuring tests are passing in all target environments then it's perhaps better to use fixtures stored on disk.

[papandreou]

Yeah, fileception suffers from the same problem :(