Would be nice if this had 0 dependencies:

import {readFileSync} from 'node:fs';
import {readFile} from 'node:fs/promises';

const parse = (uint8, options = {}) => {
  // unlike buf.toString('utf8') or or readFile(path, 'utf8'), TextDecoder will remove BOM
  let data = new TextDecoder().decode(uint8);

  if (typeof options.beforeParse === 'function') {
    data = options.beforeParse(data);
  }

  return JSON.parse(data, options.reviver);
};

export const loadJsonFile = (filePath, options) =>
  readFile(filePath).then(data => parse(data, options));

export const loadJsonFileSync = (filePath, options) =>
  parse(readFileSync(filePath), options);

It cannot seem to find the files which are there. I was able to require the file I needed as js with the same exact path save for the extension. To be sure the issue was not caused by a file path typo I did the following:

echo "{}" > file.json

Then in the importing file in the same directory:

const loadJsonFile = require('load-json-file');
 
loadJsonFile('./file.json').then(json => {
    console.log(json);
    //=> {foo: true} 
});

which produced the error:
Error: ENOENT: no such file or directory, open '. /file.json'

Does this module read file using stream or normal read ?

ref: https://travis-ci.org/iamstarkov/load-json-file/jobs/129882144#L248

as far as v0.10 and v0.12 are still LTS, i would appreciate support for this nodejs versions. what do you think?

It would be useful to be able to know what the breaking changes are in a semver-major release.

http://keepachangelog.com/ :-)

Should this module error when the json file is not found, or does this module assume that the file exists?

I have this function:

function test() {
    console.log("test function called");

    loadJsonFile(jsonpath).then(function (json) {
        console.log("json data: ", json);
    })
}

The very first console.log() statement always prints to the console, but the second console.log() statement only prints if the file at jsonpath exists, but if the json file doesn't exist, nothing happens. Should a "file not found" (ENOENT) error be included in the list of helpful errors, or should we be doing our own checks to see if the file exists before calling this module?

BTW: Thanks for all the awesome work you do!

fs/promises is only available as an import in Node.js 14: https://nodejs.org/dist/latest-v16.x/docs/api/fs.html#fs_promises_api

This breaks pkg-conf@4 under Node.js 12.

It'd be really nice to pass the file through strip-json-comments