Errors

dreamcli provides structured errors with codes, suggestions, and JSON serialization.

CLIError

import {  } from '@kjanat/dreamcli';

const  = 'production';
const  = 'us';

throw new ('Deployment failed', {
  : 'DEPLOY_FAILED',
  : 1,
  : 'Check your credentials with `mycli login`',
  : { ,  },
});

Fields

Field	Type	Description
message	string	Human-readable error message
code	string	Stable machine identifier
exitCode	number	Process exit code (default varies by type)
suggest	string	Actionable hint for the user
details	unknown	Structured payload for JSON output
cause	Error | undefined	Underlying cause (optional)

Type Safety

import {  } from '@kjanat/dreamcli';

new ('Deployment failed', {
  : 'DEPLOY_FAILED',
  exitCode: '1',
Type 'string' is not assignable to type 'number'.
});

Error Types

import {
  ,
  ,
  ,
} from '@kjanat/dreamcli';

• CLIError — base error for application-level failures
• ParseError — argv parsing failures (unknown flags, bad syntax)
• ValidationError — value validation failures (wrong type, missing required)

Parse and validation errors include "did you mean?" suggestions automatically.

Type Guards

import {
  ,
  ,
  ,
  ,
} from '@kjanat/dreamcli';

const  = ('mycli');

try {
  await .();
} catch () {
  if (()) {
    // handle parse error
  } else if (()) {
    // handle validation error
  } else if (()) {
    // handle generic CLI error
  }
}

JSON Mode

In --json mode, errors serialize to structured JSON:

{
  "error": {
    "message": "Deployment failed",
    "code": "DEPLOY_FAILED",
    "suggest": "Check your credentials with `mycli login`",
    "details": { "target": "production", "region": "us" }
  }
}

What's Next?

• Middleware — error handling in middleware chains
• Output — output channel behavior