Prevent deprecation warning in node 7.4.0

[borisdiakur]

Closes #10

[eush77]

I think that the callback should check and throw any potential errors instead of just silencing them.

[borisdiakur]

@eush77 How about printing a warning as an alternative? This wouldn’t change the current behaviour of the module (at least not drastically).

[eush77]

I don't think printing would be wise here since it leaves no way to handle the error and can mess up with the repl prompt. And this module already throw errors related to the history file since it uses openSync and closeSync.

Alternatively, would you feel positive about changing write to writeSync here?

[borisdiakur]

@eush77 The fs docs say:

Note that it is unsafe to use fs.write multiple times on the same file without waiting for the callback. For this scenario, fs.createWriteStream is strongly recommended.

So I would actually follow the recommendation and use fs.createWriteStream. What do you think?

[borisdiakur]

Ping (mr is ready to merge).

[tmpvar]

thanks - published 0.1.4