TypeError: read is not a function

[mk-pmb]

Thanks for this great module!
However, the API example code from the readme doesn't work, because the module exports an object with one method, instead of a function:

$ nodever fs-read-data
require('fs-read-data/package.json').version = 1.0.4
Node.js v8.12.0, npm v6.4.1, Ubuntu 14.04.5 LTS trusty,
kernel: 3.13.0-154-generic, machine/CPU/platform: i686 i686 i686

$ nodejs
> const read = require('fs-read-data');
undefined
> const data = read('package.json');
TypeError: read is not a function
> read
{ readFile: [Function] }

I'd prefer the function be exported directly. For compatibility, the function should get a readFile property with a self-reference until the next major version bump.

[dkebler]

@mk-pmb Agree! This is the best/simpliest package for just reading in any config file (incluing js!)

One year later still the readme is still incorrect.

For single export modules I export as default as well as named. Then one is covered.

Couple easy fixes...if @sramam doesn't do might do a PR

[mk-pmb]

A while ago I made an alias package read-data-file, primarily in hopes npm would show me what I'm looking for each time I search for "read data file". Nowadays it finally does, somewhat. Still buried below a lot of other packages, but at least on page 1 of results. That's probably as good as npm search can get.

[sramam]

Apologies - I had stopped using this package and didn't realize it was so bothersome.
I would be happy to accept a PR.