Instead of outputting the pretty-printed JSON on stdout, have an option to simply re-write the file in question with the pretty-printed JSON data. (Mainly useful in precommit-hooks and other automation tools.)

Perhaps via an -i / --in-place option, per sed.

Input to http://zaach.github.io/jsonlint/ : {"fooId":1111111111258928239}
Output:
{
"fooId": 1111111111258928300
}

Somehow the 239 in the last 3 digits becomes 300. The input integer fits within 64 bits (long type in Java). The issue is reproducible with different values and it is always the last few digits which are different. This has not been an issue for small integers (2-3 digits).

Thanks!

Hello,
I'd like to ask you to implement (and document) support for specifying multiple input files. That would allow us to run jsonlint from build (e.g. npm) scripts since we would like to pass the list of the files to lint from an environment variable. There is actually a lot of linters that accept multiple files already.

When I try to use jsonlint after a global install i get:

module.js:340
throw err;
^
Error: Cannot find module 'jsonlint'

When using the project/local install (without -g) everything works as it should.

Am I doing something wrong?

When doing a global install i get this:
$ sudo npm install jsonlint -g
npm http GET https://registry.npmjs.org/jsonlint
npm http 304 https://registry.npmjs.org/jsonlint
npm http GET https://registry.npmjs.org/nomnom
npm http GET https://registry.npmjs.org/JSV
npm http 304 https://registry.npmjs.org/nomnom
npm http 304 https://registry.npmjs.org/JSV
npm http GET https://registry.npmjs.org/underscore
npm http GET https://registry.npmjs.org/colors
npm http 304 https://registry.npmjs.org/colors
npm http 304 https://registry.npmjs.org/underscore
/usr/local/bin/jsonlint -> /usr/local/lib/node_modules/jsonlint/lib/cli.js
[email protected] /usr/local/lib/node_modules/jsonlint
├── [email protected]
└── [email protected] ([email protected], [email protected])

No errors whilst installing as you can see, just when running as above.

---EDIT------------------------------------------------------------------------

Sorry for shouting without cause, further googeling showed me the answer:

$ export NODE_PATH='/usr/local/lib/node_modules'

After this I had no more issues.

However could the install script check if there is a NODE_PATH set and warn if not that would help others like me in the future.

add a new option to allow a compact error report for easy parsing, like:

foo.json: line 3, col 6, Expecting 'STRING', '}'.

see CSSLint discussion about this subject.

that way it can be easily integrated into other tools like Vim or any other IDE.

npm ERR! Unsupported
npm ERR! Not compatible with your version of node/npm: [email protected]
npm ERR! Required: {"node":"0.4 || 0.5"}
npm ERR! Actual: {"npm":"1.0.104","node":"0.6.0"}

I am using this as my builder / linter in Sublime Text 2. It would be helpful to have a '-q' option, so I can just see the errors. (In my case, just redirecting to '/dev/null' isn't an option.

Recipe for the curious:

{
    "cmd": ["jsonlint", "$file"],
    "selector": "source.json",
    "path": "/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin"
}

I had an app that was giving unterminated string constant exceptions in jQuery/Firefox and Illegal Character exceptions in jQuery/Chrome. I ran my JSON content through JSONLint and it reported the content as valid.

After looking into it, I found that my JSON had unescaped unicode characters (smart quotes).

I modified my code to escape unicode chars in the format \uxxxx and my app is now working.

So, it looks like jsonlint is passing as correct JSON content that has unicode and that's not correct.

I want to be able to pipe a curl request into this awesome package

like

$curl http://API/ping.js |jsonlint

this is not valid
{
'a': 'b'
}

but this is valid
{
"a" : "b"
}
i think single quote strings are valid in javascript

The test called "test null literal", actually tests the number 1234.

https://github.com/zaach/jsonlint/blob/master/test/all-tests.js#L48

exports["test null literal"] = function () {
    var json = '1234';
    assert.equal(parser.parse(json), 1234);
};

Looks like a copy paste error from the previous test.

-s option doesn't sort keys in the below example. 'jsonlint -s testcase.json' returns the same json as input. Obviously, "w" should follow "a".

--- testcase.json ---
[[{
"w": "",
"a": 4
}]]

version 1.6.0

Hi,

Really dig your module, however when I tried to use in my module and output the json via console.log I got the following outputs:

WebserverCPUAlarmHigh: { Type: 'AWS::CloudWatch::Alarm', Properties: [Object] },
WebserverCPUAlarmLow: { Type: 'AWS::CloudWatch::Alarm', Properties: [Object] } },

Notice the [Object] portion... Not sure why its not outputting straight json?

Here's my code: https://gist.github.com/Hesse/6513835

For various reasons, I'd quite like the pretty-printed JSON to have it's object-keys sorted on output (mainly sane diff'ing). Either optionally or forced (like Python's json-module).

Please add an option for C-style object and array braces.

Java-style (current):

{
    "foo" : {
        "bar" : 10
    },
    "lol" : [
        "rofl",
        "lmao"
    ]
}

C-style:

{
    "foo" :
    {
        "bar" : 10
    },
    "lol" :
    [
        "rofl",
        "lmao"
    ]
}

Strings which look like JSON arrays are parsed as arrays (and will throw an error.)

For example:
"pos": "[106.675,525.792,47.7364]" is entirely valid JSON but will error out with Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[' when linted.

I can't currently install your package.json file with NPM. Please update to fix it, thanks!

I'm pretty sure tests are not needed in production. :)
They just bloat project dependencies, install time, use bandwidth, etc.

You could either use the package.json files property to whitelist files for production or .npmignore to blacklist unneeded ones.

For more info on .npmignore and an automatic generator see https://github.com/inikulin/dmn

Hi, it seems that jsonlint is already v1.6.2 now.
Would you like to add tags for the new released versions?
Thank you!

Right now the default error messages are pretty hard to parse by humans. It would be great if the error messages could be a bit friendlier, such as:

The 'foo' property is missing and is required.

Or

The 'foo' property should be a string but is a number.

Is it possible to output the line number of line of a place where the schema error occured?
If that is possible, then it can be parsed by the text editors to show where
user mistakingly typed an error, resulting more ease on editing the text...

Thanks for offering jsonlint via npm, works great.

I stumbled upon one issue though: when I try to browserify jsonlint, an error is thrown:

Error: Cannot find module 'file' from '/home/ubuntu/workspace/node_modules/jsonlint/lib'

The module file is required here in the source code:
https://github.com/zaach/jsonlint/blob/master/lib/jsonlint.js#L424

It looks like the "file" module is missing from the dependencies in package.json. But maybe this code is redundant anyway: I guess if you're not running node.js (i.e. typeof process === 'undefined'), the file module won't work either?

right now if you use import jsonlint from 'jsonlint'; e.g. via browserify/babel it doesn't have an export -- there's no export statement in web/ folder

I'm using the checker under web/
In Internet Explorer 11, if you paste this text
::
{

"Accept-Language": "en-US,en;q=0.8"

"Host": "headers.jsontest.com",

"Accept-Charset": "ISO-8859-1,utf-8;q=0.7,;q=0.3",
"Accept": "text/html,application/xhtml+xml,application/xml;q=0.9,/*;q=0.8"
}

you get an [Object error], instead of a parse fail.

Hello,

1. which json-schema-draft versions are supported?
2. could you please add support for json-schema-draft-04?
   (where in the code is it configured?)

https://docs.npmjs.com/files/package.json#license

RT

If you give jsonlint the --pretty-print option with invalid json, then jsonlint prints an error message (good), outputs its best guess at formatted json (good), but exits with status 0 (bad). Perhaps this means that the parsing succeeded, but this makes it difficult to detect whether the input is valid json.

Expected behavior: exit status is 0 if input valid json, 1 otherwise.

(jsonlint 1.6.0, node v 0.10.0 on OS X 10.6.8)

example:

{
"action": "log in"
}

output:

Error: Parse error on line 2:
{ "action": "log in"}
---------------^
Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'undefined'

expected output:

JSON is valid!

The package in the npm registry (http://search.npmjs.org/#/jsonlint) has not been updated for node 0.6+.

I can't seem to find licensing information for this package anywhere. Something like BSD would be great, but of course that's up to you, as long as the terms are clear.

1. paste the following code to jsonlint

   {
     "s": "\\"
   }

2. make sure the checkbox reformat JSON is checked, then click validate button many times

The backslash will continue to repeat itself

The following console interaction should explain the issue.

$ curl http://host/file.json | jsonlint | head -4
{
  "some-key": "some-value",
  "array": [
    {

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: write EPIPE
    at errnoException (net.js:904:11)
    at Object.afterWrite (net.js:720:19)

Is there a way to know that the closed output pipe is not an error?

I've noticed a couple of issues in the reformatted output when there's escapes in the input:

1. disappearing slashes. This represents a two-character string, not a newline escape:

   • in: "\\n"
   • expected out: "\\n"
   • actual out: "\n"

   This also happens for b, r, f, and t.

2. unexpected slashes.

   • in: "\u0066"
   • expected out: "f" (or "\u0066")
   • actual out: "\\u0066"

diff --git a/lib/cli.js b/lib/cli.js
index 068fcf1..dce6845 100755
--- a/lib/cli.js
+++ b/lib/cli.js
@@ -47,14 +47,20 @@ function parse (source) {
 }

 function main (args) {
-  var source = '';
+  var source = '',
+      parsedSource = '';
    if (options.file) {
     var path = require('path').join(process.cwd(), options.file); 
     source = fs.readFileSync(path, "utf8");
+    parsedSource = parse(source);
     if (options.inplace) {
-      fs.writeSync(fs.openSync(path,'w+'), parse(source), 0, "utf8");
+      if (parsedSource) {
+        fs.writeSync(fs.openSync(path,'w+'), parsedSource, 0, "utf8");
+      } else {
+        sys.error("JSON contained errors - not overwriting file");
+      }
     } else {
-      sys.puts(parse(source));
+      sys.puts(parsedSource);
     }
   } else {
     var stdin = process.openStdin();

It's slightly more complicated as I'd like to write an error message, but it seem the parser kills the program right away on errors. But if I don't check if the parser acutally returned anything, it writes out an empty file...

I'd love to lint multiple json files in a single go, and get a report of each failure, but: jsontlint project/**/*.json doesn't seem to do the job. When linting multiple files it'd probably make sense to not output pretty-printed json when a file passes - simply return the errors.

What do you think?

I personally prefer four spaces, and I know quite a few who prefer tabs (&c). Perhaps an --indent <whatever> option?

The website http://jsonlint.com/ says it is based on this library. However, that site has the following bug: it rejects valid JSON that is NOT an object or an array. These strings are all valid JSON:

1
12
12.34
"string"
true
false
null

Should this be corrected in this library?

Hi. Do you intend to add a feature to validate json against schemas?

Otherwise, I'll use JSV library although it has no CLI

I was looking over the issues and was planning to send some pull requests but when i realized there were issues from 2011 I wanted to be sure they would be looked at before giving an attempt.

npm WARN [email protected] dependencies field should be hash of : pairs
/usr/local/bin/jsonlint -> /usr/local/lib/node_modules/jsonlint/lib/cli.js
[email protected] /usr/local/lib/node_modules/jsonlint
└── [email protected]

I am having this warning message at the end of jsonlint installation. Although that message jsonlint seems to be working fine. But again I would like to learn what it is.

Thanks.

Please show where the error happens and what should be there instead. Because currently it says json error at this file. there is no line or what to replace instead.

I'm trying to lint some JSON files that happen to have some comments in JSON like this:

// this is configuration specific to aws deployments
{
  // disable statsd for aws
  "statsd": {
    "enabled": false
  }
}

But the $ jsonlint config/aws.json command gives me the following:

$ jsonlint config/aws.json
[Error: Parse error on line 1:
// this is configura
^
Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'undefined']

I'm not sure what libs mozilla/persona is using to load the commented JSON, but a bunch of the files are failing jsonlint due to the comments.

Quiet + file:

$ echo "{ 'single-quoted': 'thus-bad-json' }" > /tmp/bad.json
$ jsonlint -c -q /tmp/bad.json ; echo $?
/tmp/bad.json: line 1, col 1, found: 'INVALID' - expected: 'STRING', '}'.
1

Quiet + STDIN:

$ echo "{ 'single-quoted': 'thus-bad-json' }" | jsonlint -c -q -; echo $?
0

Resolved with following patch:

--- /usr/local/bin/jsonlint.orig        2013-11-28 11:43:41.000000000 +0100
+++ /usr/local/bin/jsonlint     2013-11-28 11:44:48.000000000 +0100
@@ -147,7 +147,8 @@ function main (args) {
       source += chunk.toString('utf8');
     });
     stdin.on('end', function () {
-      if (! options.quiet) {console.log(parse(source))};
+      source = parse(source);
+      if (! options.quiet) {console.log(source)};
     });
   }
 }

Behaviour after patch:

$ echo "{ 'single-quoted': 'thus-bad-json' }" | jsonlint -c -q -; echo $?
line 1, col 1, found: 'INVALID' - expected: 'STRING', '}'.
1

I developed a vim plugin called sourcebeautify using jsonlint.js as it's error checker and beautifier.

The script hosted on vim.org aslo, link

Thanks for this cool project!