fix script fails on Windows

[rishi-raj-jain]

fixes #37

the fix uses unlink-self if available via node, so that it can run agnostic to the OS

[imballinst]

I noticed that the only time node-read-yaml is required is in here, in a test file that would never be run by a consumer:

node-read-yaml/test.js

Line 6 in 3c0a9fd

const read = require('node-read-yaml');

That being the case, I think it's better to these?

1. Just do require('.') (which will point to index.js)
2. Remove the preinstall script
3. Remove the node-read-yaml in devDependencies

[rishi-raj-jain]

I noticed that the only time node-read-yaml is required is in here, in a test file that would never be run by a consumer:

node-read-yaml/test.js

Line 6 in 3c0a9fd

const read = require('node-read-yaml');

That being the case, I think it's better to these?

1. Just do require('.') (which will point to index.js)
2. Remove the preinstall script
3. Remove the node-read-yaml in devDependencies

But we can not remove the pre install script since it unlinks the package if it has the ability to

[imballinst]

But we can not remove the pre install script since it unlinks the package if it has the ability to

Maybe the repository owner has the better knowledge of it, but from my perspective, here's the flow:

1. This package is referring its own in devDependencies here: https://github.com/dailyrandomphoto/node-read-yaml/blob/master/package.json#L22
2. In order to prevent endless circular reference (I assume), the repository owner creates another package called unlink-self https://github.com/dailyrandomphoto/unlink-self, which purpose is only to delete node_modules/node-read-yaml.

If we just simply not have node-read-yaml in the devDependencies, that solves everything, right?

[rishi-raj-jain]

Ah oh yes, you are right!