weisjohn / jsonload

read in a json file (supports line-delimited files)

jsonload

read in a json file, handles line-delimited

usage

var jsonload = require('jsonload');

// async
jsonload('./foo', function(err, results) {
    console.log(results);
});

// sync
var foo = jsonload.sync('./foo');

errors

Because jsonload handles simple and line-delimited JSON files, there are a three possible errors that may be returned/thrown:

• file not found
• an invalid JSON file
• an invalid JSON line(s)

// async
jsonload('./foo', function(err, results) {
    if (err.code == 'ENOENT')
        console.log('file not found');
    if (err.name == 'SyntaxError')
        console.log('invalid JSON file');
    if (err.length)
        console.log('invalid JSON lines', e);

    // on complex files, there may be lines which parsed correctly
    console.log(results);
});

// sync
try {
    var foo = jsonload.sync('./foo');
} catch (err) {
    if (err.code == 'ENOENT')
        console.log('file not found');
    if (err.name == 'SyntaxError')
        console.log('invalid JSON file');
    if (err.length)
        console.log('invalid JSON lines', e);
}

parser

By default, jsonload utilizes the built-in JSON parser. You can optionally specify a different parser. It must be an object with a .parse() function:

var EJSON = require('mongodb-extended-json');
var sync = jsonload.sync('./ejson-file', EJSON);

jsonload('./ejson-file', EJSON, function(err, ejson) {
    console.log(ejson[0]);
});

The parser is invoked line-by-line. To log each line before parsing (tap-style):

jsonload('./json-file', { parse: function(obj) {
    console.log(obj);
    return JSON.parse(obj);
} }, function() {});

jsonload's Issues

optional parser argument

Currently, we utilize JSON.parse(), but if we could pass in a different parser, projects like mongoose-simple-fixtures could utilize it.

doesn't work on node <= 0.12

This function call doesn't exist in https://nodejs.org/docs/latest-v0.10.x/api/path.html and based on https://github.com/nodejs/node/blob/2c33819/lib/path.js#L212 and https://github.com/nodejs/node/blob/2c33819/lib/path.js#L469 it doesn't look trivial to reimplement perfectly.

We should either specify a engine property in package.json or simply skip the resolution.

custom parser is not honored when using require() style

When invoked with a custom parser, we dishonor that request by using require(). Instead, we should attempt to read the file, then use the custom parser.

affected areas:

jsonload/index.js

Lines 58 to 60 in e71603b

	// simple style
	var err;
	try { return cb(null, require(path)); } catch (e) { err = e; }

and

jsonload/index.js

Lines 74 to 76 in e71603b

	// simple
	var err;
	try { return require(path); } catch (e) { err = e; }

exposed by weisjohn/mongoose-prime#4