Skip to content

cli: pbjs/pbts print full stack traces for ordinary user errors #15

Description

@JavaGT

Lane: CLI/UX (sweep 3, F1)
cli/bin/pbjs and bin/pbts only forward numeric exits; every error path throws (cli/pbjs.js:372,403,419,441,461; cli/pbts.js:182,263), so ordinary user errors (missing file, parse error, bad target, bad -o dir) print full Node stack traces with internal frames and leak library paths. Reproduced live for five error classes.

Verdicts: luna Confirm Strong; grok Downgrade Worth exploring (noisy DX, not data loss). Recorded as Worth exploring.

Upstream: unreported.

Decision question: Adopt — catch at the bin level, print err.message to stderr, exit 1, stacks behind NODE_DEBUG/--stack?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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