[BUG] bad error npm ci with bad package.json

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

i have a trailing comma in a json object in a package.json

running npm install prints this:

npm ERR! code EJSONPARSE
npm ERR! path /usr/origami/package.json
npm ERR! JSON.parse Unexpected token "}" (0x7D) in JSON at position 703 while parsing near "honk'\",\n  },\n  \"repository\": {..."
npm ERR! JSON.parse Failed to parse JSON data.
npm ERR! JSON.parse Note: package.json must be actual JSON, not just JavaScript.

npm ERR! A complete log of this run can be found in:
npm ERR!     /usr/large.rabbit/.npm/_logs/2021-11-02T17_42_41_387Z-debug.log

running npm ci prints this

npm ERR! The `npm ci` command can only install with an existing package-lock.json or
npm ERR! npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or
npm ERR! later to generate a package-lock.json file, then try again.

npm ERR! A complete log of this run can be found in:
npm ERR!     /usr/large.rabbit/.npm/_logs/2021-11-02T17_42_36_923Z-debug.log

Expected Behavior

npm ci should print the helpful message like npm install

Steps To Reproduce

1. have a trailing comma in a json object in a package.json
2. run npm ci

Environment

• OS: don't know
• Node: 16
• npm: 8.1.0

Reproduce the behavior with a malformed package.json containing a trailing comma, then compare the npm ci and npm install error paths. The change is done when npm ci reports the helpful JSON parse message shown for npm install; no source file or test is identified in the issue.