Why NDJSON instead of JSON?

[alexandernst]

yarn info (and others?) output NDJSON instead of JSON and I can't find a reason why you'd have picked NDJSON instead of JSON.

JSON is already very easily parseable with jq and the size increase in the output is negligible compared to NDJSON. Maybe switch to JSON and make it easier to parse yarn's output?

[Daniel15]

jq should handle newline-delimited JSON fine.

Are you talking about Yarn 1.x or 4.x? This repo is for 1.x, which is frozen and not getting updates.

[alexandernst]

Sure, jq can handle NDJSON, but why pick NDJSON instead of plain JSON in the first place? It just seems a weird decision given the fact that NDJSON is not that common and, albeit jq handling it properly, there most probably are ton of other tools that wont handle NDJSON.

I believe the output of this particular command is the same for 1.x and 4.x.

[yukha-dw]

I think what you mean is not NDJSON but something like Object on Javascript?

{
  id: 123,
  name: "John Doe",
  age: 1
}

you can add --json to return as JSON
https://classic.yarnpkg.com/lang/en/docs/cli/info/#toc-yarn-info