Skip to content

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

@CodeDeficient

Description

@CodeDeficient

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions