"A JSON text must at least contain two octets! (JSON::ParserError)" error for npm-based project about licensed HOT 4 CLOSED

@ispringer thanks for the report!

A more informative error message sounds like a great idea. if you'd like to open a PR fixing this that would be great. Otherwise I'm not sure when I'll have a chance to get to it.

FYI for more short-term investigation purposes, the parsed json comes from npm list --json --production --long

from licensed.

Hi @jonabc,

Thanks for the reply. I ran that command and I got a bunch of errors on stderr. The errors appear to be because my package.json file is actually intended for yarn, and uses some syntax that is not npm-compatible. Note, I was able to parse the JSON from stdout without any errors using JSON.parse via node, so maybe Licensed is trying to parse both stdout+stderr, rather than only stdout, as JSON?

from licensed.

@ispringer Licensed only parses stdout, but intentionally does not use stdout from shell commands that exit with an error code. This avoids picking up information that might be incorrect or out of date if a CLI tool finds an error.

So it sounds like there are two things that would be helpful here

1. a yarn source that is different from the npm source that is being used
   • it looks like yarn.lock is the indicator that yarn is used in the local directory
2. a more helpful error message when the npm command fails or output can't be parsed.

I'll open a new issue to create a yarn source to track that request separately.

from licensed.

A friendlier error message from npm (and other shelled-out commands) is now a reality: #38.

from licensed.