package.json and package-lock.json disagree on bin entry point #13

What

package.json declares the bin as:

"bin": { "karpeslop": "karpeslop-cli.js" }

package-lock.json declares the bin as:

"bin": { "karpeslop": "karpeslop-bin.js" }

Impact

npm uses the lockfile to resolve the installed bin. This resolves itself on the next npm install, but until then the two files are inconsistent. If only one entry point actually exists on disk, whichever doesn't will fail when invoked.

Fix

Set both to the correct entry point (likely karpeslop-cli.js). Run npm install to regenerate the lockfile after fixing package.json.