Invalid package.json: JSONParseError: Unexpected end of JSON input while parsing near

[doug-wade]

» npx @tybalt/cli scaffold eleventy --name wombat
stdout:

Wrote to /home/doug/workspace/website/wombat/package.json:

{
  "name": "wombat",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC"
}




installing dependencies; there may be errors
adding the following scripts to package.json
    test: run the unit tests
    build: build the static website
    serve: serve the local development website


node:internal/errors:865
  const err = new Error(message);
              ^

Error: Command failed: npm pkg set 'scripts.serve'='eleventy --serve'
npm ERR! code EJSONPARSE
npm ERR! JSON.parse Invalid package.json: JSONParseError: Unexpected end of JSON input while parsing near "...ds\": [],\n  \"author\": "
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: /home/doug/.npm/_logs/2023-08-04T16_03_18_001Z-debug-0.log

    at ChildProcess.exithandler (node:child_process:419:12)
    at ChildProcess.emit (node:events:514:28)
    at maybeClose (node:internal/child_process:1091:16)
    at ChildProcess._handle.onexit (node:internal/child_process:302:5) {
  code: 1,
  killed: false,
  signal: null,
  cmd: "npm pkg set 'scripts.serve'='eleventy --serve'",
  stdout: '',
  stderr: 'npm ERR! code EJSONPARSE\n' +
    'npm ERR! JSON.parse Invalid package.json: JSONParseError: Unexpected end of JSON input while parsing near "...ds\\": [],\\n  \\"author\\": "\n' +
    'npm ERR! JSON.parse Failed to parse JSON data.\n' +
    'npm ERR! JSON.parse Note: package.json must be actual JSON, not just JavaScript.\n' +
    '\n' +
    'npm ERR! A complete log of this run can be found in: /home/doug/.npm/_logs/2023-08-04T16_03_18_001Z-debug-0.log\n'
}

Node.js v18.17.0

[doug-wade]

I'm wondering if we're racing with the creation of package.json? I also wonder if users run npm init first, if that would work around the issue?