Skip to content

Consider exiting with non-zero on invalid cli usage #691

@lread

Description

@lread

version
v0.8.152

problem
When I make a typo on the squint command line, it exits with success (zero).
This is not a big issue for interactive use, but most folks would like their build scripts to fail fast if they've invoked squint incorrectly.

repro

npx squint blarg

expected behavior
Exit with non-zero with incorrect usage error (and perhaps, usage help).

actual behavior
squint emits no output and exits with zero.

next steps
Happy to create a PR if you agree that this is interesting to address.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions