refactor: centralize error handling with typed error classes by wyattjoh · Pull Request #24 · clerk/cli

wyattjoh · 2026-03-10T18:42:11Z

What

Introduce a typed error hierarchy (CliError, UserAbortError, ApiError, BapiError, PlapiError) in src/lib/errors.ts with standardized exit codes
Add a single top-level error handler in cli.ts that catches all typed errors and formats output consistently
Add --verbose flag for detailed API error output
Add SIGINT handler that exits with code 130
Add oxlint configuration (.oxlintrc.json)

Why

Error handling was scattered across every command — each had its own try/catch + console.error + process.exit with inconsistent formatting, exit codes, and messaging. This made it difficult to maintain consistent UX and meant every new command had to reimplement error handling. Centralizing it ensures uniform behavior and reduces per-command boilerplate.

How

Created src/lib/errors.ts with a class hierarchy: CliError for general CLI errors, ApiError (with BapiError/PlapiError subclasses) for HTTP failures, and UserAbortError for prompt cancellations. Helper functions usageError() and userAbort() provide ergonomic throwing.
Wrapped program.parseAsync() in a main() function with a centralized catch that dispatches on error type — clean exit for aborts, red-formatted messages for CLI errors, labeled API error details for API failures.
Updated all commands to throw typed errors instead of handling exits locally.
Updated all tests to assert on thrown errors rather than spying on process.exit.

AIE-626

Replace scattered try/catch + console.error + process.exit patterns with a typed error hierarchy (CliError, ApiError, BapiError, PlapiError, UserAbortError) and a single top-level error handler in cli.ts. Commands now throw typed errors instead of handling exits locally, making error behavior consistent and testable. Adds --verbose flag for detailed API error output and SIGINT handling.

Add `context` field to `ApiError` and `withApiContext()` utility to attach human-readable operation context at call sites without verbose try/catch blocks. Drop internal "Platform API"/"Backend API" labels from the global error handler.

Bun's test runner doesn't fully clear process.exitCode when set to undefined, causing the test file to exit with code 1 despite all assertions passing.

brkalow · 2026-03-11T03:59:46Z

 .action(deploy);

-program.parse();
+function formatApiBody(body: string, verbose: boolean): string {


consider making this a method on ApiError

brkalow

Looks good, do you think there are any meaningful additions to AGENTS.md to be made to ensure this pattern is followed?

…ndling - Rename usageError/userAbort to throwUsageError/throwUserAbort to make the never-returning throw behavior explicit at call sites - Auto-append .md to Clerk docs URLs in agent mode so agents receive raw markdown instead of rendered HTML

wyattjoh · 2026-03-10T18:42:11Z

What

Introduce a typed error hierarchy (CliError, UserAbortError, ApiError, BapiError, PlapiError) in src/lib/errors.ts with standardized exit codes
Add a single top-level error handler in cli.ts that catches all typed errors and formats output consistently
Add --verbose flag for detailed API error output
Add SIGINT handler that exits with code 130
Add oxlint configuration (.oxlintrc.json)

Why

Error handling was scattered across every command — each had its own try/catch + console.error + process.exit with inconsistent formatting, exit codes, and messaging. This made it difficult to maintain consistent UX and meant every new command had to reimplement error handling. Centralizing it ensures uniform behavior and reduces per-command boilerplate.

How

Created src/lib/errors.ts with a class hierarchy: CliError for general CLI errors, ApiError (with BapiError/PlapiError subclasses) for HTTP failures, and UserAbortError for prompt cancellations. Helper functions usageError() and userAbort() provide ergonomic throwing.
Wrapped program.parseAsync() in a main() function with a centralized catch that dispatches on error type — clean exit for aborts, red-formatted messages for CLI errors, labeled API error details for API failures.
Updated all commands to throw typed errors instead of handling exits locally.
Updated all tests to assert on thrown errors rather than spying on process.exit.

AIE-626

Replace scattered try/catch + console.error + process.exit patterns with a typed error hierarchy (CliError, ApiError, BapiError, PlapiError, UserAbortError) and a single top-level error handler in cli.ts. Commands now throw typed errors instead of handling exits locally, making error behavior consistent and testable. Adds --verbose flag for detailed API error output and SIGINT handling.

Add `context` field to `ApiError` and `withApiContext()` utility to attach human-readable operation context at call sites without verbose try/catch blocks. Drop internal "Platform API"/"Backend API" labels from the global error handler.

Bun's test runner doesn't fully clear process.exitCode when set to undefined, causing the test file to exit with code 1 despite all assertions passing.

brkalow · 2026-03-11T03:59:46Z

 .action(deploy);

-program.parse();
+function formatApiBody(body: string, verbose: boolean): string {


consider making this a method on ApiError

brkalow

Looks good, do you think there are any meaningful additions to AGENTS.md to be made to ensure this pattern is followed?

…ndling - Rename usageError/userAbort to throwUsageError/throwUserAbort to make the never-returning throw behavior explicit at call sites - Auto-append .md to Clerk docs URLs in agent mode so agents receive raw markdown instead of rendered HTML

wyattjoh · 2026-03-10T18:42:11Z

What

Introduce a typed error hierarchy (CliError, UserAbortError, ApiError, BapiError, PlapiError) in src/lib/errors.ts with standardized exit codes
Add a single top-level error handler in cli.ts that catches all typed errors and formats output consistently
Add --verbose flag for detailed API error output
Add SIGINT handler that exits with code 130
Add oxlint configuration (.oxlintrc.json)

Why

Error handling was scattered across every command — each had its own try/catch + console.error + process.exit with inconsistent formatting, exit codes, and messaging. This made it difficult to maintain consistent UX and meant every new command had to reimplement error handling. Centralizing it ensures uniform behavior and reduces per-command boilerplate.

How

Created src/lib/errors.ts with a class hierarchy: CliError for general CLI errors, ApiError (with BapiError/PlapiError subclasses) for HTTP failures, and UserAbortError for prompt cancellations. Helper functions usageError() and userAbort() provide ergonomic throwing.
Wrapped program.parseAsync() in a main() function with a centralized catch that dispatches on error type — clean exit for aborts, red-formatted messages for CLI errors, labeled API error details for API failures.
Updated all commands to throw typed errors instead of handling exits locally.
Updated all tests to assert on thrown errors rather than spying on process.exit.

AIE-626

Replace scattered try/catch + console.error + process.exit patterns with a typed error hierarchy (CliError, ApiError, BapiError, PlapiError, UserAbortError) and a single top-level error handler in cli.ts. Commands now throw typed errors instead of handling exits locally, making error behavior consistent and testable. Adds --verbose flag for detailed API error output and SIGINT handling.

Add `context` field to `ApiError` and `withApiContext()` utility to attach human-readable operation context at call sites without verbose try/catch blocks. Drop internal "Platform API"/"Backend API" labels from the global error handler.

Bun's test runner doesn't fully clear process.exitCode when set to undefined, causing the test file to exit with code 1 despite all assertions passing.

brkalow · 2026-03-11T03:59:46Z

 .action(deploy);

-program.parse();
+function formatApiBody(body: string, verbose: boolean): string {


consider making this a method on ApiError

brkalow

Looks good, do you think there are any meaningful additions to AGENTS.md to be made to ensure this pattern is followed?

…ndling - Rename usageError/userAbort to throwUsageError/throwUserAbort to make the never-returning throw behavior explicit at call sites - Auto-append .md to Clerk docs URLs in agent mode so agents receive raw markdown instead of rendered HTML

wyattjoh · 2026-03-10T18:42:11Z

What

Introduce a typed error hierarchy (CliError, UserAbortError, ApiError, BapiError, PlapiError) in src/lib/errors.ts with standardized exit codes
Add a single top-level error handler in cli.ts that catches all typed errors and formats output consistently
Add --verbose flag for detailed API error output
Add SIGINT handler that exits with code 130
Add oxlint configuration (.oxlintrc.json)

Why

Error handling was scattered across every command — each had its own try/catch + console.error + process.exit with inconsistent formatting, exit codes, and messaging. This made it difficult to maintain consistent UX and meant every new command had to reimplement error handling. Centralizing it ensures uniform behavior and reduces per-command boilerplate.

How

Created src/lib/errors.ts with a class hierarchy: CliError for general CLI errors, ApiError (with BapiError/PlapiError subclasses) for HTTP failures, and UserAbortError for prompt cancellations. Helper functions usageError() and userAbort() provide ergonomic throwing.
Wrapped program.parseAsync() in a main() function with a centralized catch that dispatches on error type — clean exit for aborts, red-formatted messages for CLI errors, labeled API error details for API failures.
Updated all commands to throw typed errors instead of handling exits locally.
Updated all tests to assert on thrown errors rather than spying on process.exit.

AIE-626

Replace scattered try/catch + console.error + process.exit patterns with a typed error hierarchy (CliError, ApiError, BapiError, PlapiError, UserAbortError) and a single top-level error handler in cli.ts. Commands now throw typed errors instead of handling exits locally, making error behavior consistent and testable. Adds --verbose flag for detailed API error output and SIGINT handling.

Add `context` field to `ApiError` and `withApiContext()` utility to attach human-readable operation context at call sites without verbose try/catch blocks. Drop internal "Platform API"/"Backend API" labels from the global error handler.

Bun's test runner doesn't fully clear process.exitCode when set to undefined, causing the test file to exit with code 1 despite all assertions passing.

brkalow · 2026-03-11T03:59:46Z

 .action(deploy);

-program.parse();
+function formatApiBody(body: string, verbose: boolean): string {


consider making this a method on ApiError

brkalow

Looks good, do you think there are any meaningful additions to AGENTS.md to be made to ensure this pattern is followed?

…ndling - Rename usageError/userAbort to throwUsageError/throwUserAbort to make the never-returning throw behavior explicit at call sites - Auto-append .md to Clerk docs URLs in agent mode so agents receive raw markdown instead of rendered HTML

wyattjoh · 2026-03-10T18:42:11Z

What

Introduce a typed error hierarchy (CliError, UserAbortError, ApiError, BapiError, PlapiError) in src/lib/errors.ts with standardized exit codes
Add a single top-level error handler in cli.ts that catches all typed errors and formats output consistently
Add --verbose flag for detailed API error output
Add SIGINT handler that exits with code 130
Add oxlint configuration (.oxlintrc.json)

Why

Error handling was scattered across every command — each had its own try/catch + console.error + process.exit with inconsistent formatting, exit codes, and messaging. This made it difficult to maintain consistent UX and meant every new command had to reimplement error handling. Centralizing it ensures uniform behavior and reduces per-command boilerplate.

How

Created src/lib/errors.ts with a class hierarchy: CliError for general CLI errors, ApiError (with BapiError/PlapiError subclasses) for HTTP failures, and UserAbortError for prompt cancellations. Helper functions usageError() and userAbort() provide ergonomic throwing.
Wrapped program.parseAsync() in a main() function with a centralized catch that dispatches on error type — clean exit for aborts, red-formatted messages for CLI errors, labeled API error details for API failures.
Updated all commands to throw typed errors instead of handling exits locally.
Updated all tests to assert on thrown errors rather than spying on process.exit.

AIE-626

Replace scattered try/catch + console.error + process.exit patterns with a typed error hierarchy (CliError, ApiError, BapiError, PlapiError, UserAbortError) and a single top-level error handler in cli.ts. Commands now throw typed errors instead of handling exits locally, making error behavior consistent and testable. Adds --verbose flag for detailed API error output and SIGINT handling.

Add `context` field to `ApiError` and `withApiContext()` utility to attach human-readable operation context at call sites without verbose try/catch blocks. Drop internal "Platform API"/"Backend API" labels from the global error handler.

Bun's test runner doesn't fully clear process.exitCode when set to undefined, causing the test file to exit with code 1 despite all assertions passing.

brkalow · 2026-03-11T03:59:46Z

 .action(deploy);

-program.parse();
+function formatApiBody(body: string, verbose: boolean): string {


consider making this a method on ApiError

brkalow

Looks good, do you think there are any meaningful additions to AGENTS.md to be made to ensure this pattern is followed?

…ndling - Rename usageError/userAbort to throwUsageError/throwUserAbort to make the never-returning throw behavior explicit at call sites - Auto-append .md to Clerk docs URLs in agent mode so agents receive raw markdown instead of rendered HTML

wyattjoh · 2026-03-10T18:42:11Z

What

Introduce a typed error hierarchy (CliError, UserAbortError, ApiError, BapiError, PlapiError) in src/lib/errors.ts with standardized exit codes
Add a single top-level error handler in cli.ts that catches all typed errors and formats output consistently
Add --verbose flag for detailed API error output
Add SIGINT handler that exits with code 130
Add oxlint configuration (.oxlintrc.json)

Why

Error handling was scattered across every command — each had its own try/catch + console.error + process.exit with inconsistent formatting, exit codes, and messaging. This made it difficult to maintain consistent UX and meant every new command had to reimplement error handling. Centralizing it ensures uniform behavior and reduces per-command boilerplate.

How

Created src/lib/errors.ts with a class hierarchy: CliError for general CLI errors, ApiError (with BapiError/PlapiError subclasses) for HTTP failures, and UserAbortError for prompt cancellations. Helper functions usageError() and userAbort() provide ergonomic throwing.
Wrapped program.parseAsync() in a main() function with a centralized catch that dispatches on error type — clean exit for aborts, red-formatted messages for CLI errors, labeled API error details for API failures.
Updated all commands to throw typed errors instead of handling exits locally.
Updated all tests to assert on thrown errors rather than spying on process.exit.

AIE-626

Replace scattered try/catch + console.error + process.exit patterns with a typed error hierarchy (CliError, ApiError, BapiError, PlapiError, UserAbortError) and a single top-level error handler in cli.ts. Commands now throw typed errors instead of handling exits locally, making error behavior consistent and testable. Adds --verbose flag for detailed API error output and SIGINT handling.

Add `context` field to `ApiError` and `withApiContext()` utility to attach human-readable operation context at call sites without verbose try/catch blocks. Drop internal "Platform API"/"Backend API" labels from the global error handler.

Bun's test runner doesn't fully clear process.exitCode when set to undefined, causing the test file to exit with code 1 despite all assertions passing.

brkalow · 2026-03-11T03:59:46Z

 .action(deploy);

-program.parse();
+function formatApiBody(body: string, verbose: boolean): string {


consider making this a method on ApiError

brkalow

Looks good, do you think there are any meaningful additions to AGENTS.md to be made to ensure this pattern is followed?

…ndling - Rename usageError/userAbort to throwUsageError/throwUserAbort to make the never-returning throw behavior explicit at call sites - Auto-append .md to Clerk docs URLs in agent mode so agents receive raw markdown instead of rendered HTML

wyattjoh · 2026-03-10T18:42:11Z

What

Introduce a typed error hierarchy (CliError, UserAbortError, ApiError, BapiError, PlapiError) in src/lib/errors.ts with standardized exit codes
Add a single top-level error handler in cli.ts that catches all typed errors and formats output consistently
Add --verbose flag for detailed API error output
Add SIGINT handler that exits with code 130
Add oxlint configuration (.oxlintrc.json)

Why

Error handling was scattered across every command — each had its own try/catch + console.error + process.exit with inconsistent formatting, exit codes, and messaging. This made it difficult to maintain consistent UX and meant every new command had to reimplement error handling. Centralizing it ensures uniform behavior and reduces per-command boilerplate.

How

Created src/lib/errors.ts with a class hierarchy: CliError for general CLI errors, ApiError (with BapiError/PlapiError subclasses) for HTTP failures, and UserAbortError for prompt cancellations. Helper functions usageError() and userAbort() provide ergonomic throwing.
Wrapped program.parseAsync() in a main() function with a centralized catch that dispatches on error type — clean exit for aborts, red-formatted messages for CLI errors, labeled API error details for API failures.
Updated all commands to throw typed errors instead of handling exits locally.
Updated all tests to assert on thrown errors rather than spying on process.exit.

AIE-626

Replace scattered try/catch + console.error + process.exit patterns with a typed error hierarchy (CliError, ApiError, BapiError, PlapiError, UserAbortError) and a single top-level error handler in cli.ts. Commands now throw typed errors instead of handling exits locally, making error behavior consistent and testable. Adds --verbose flag for detailed API error output and SIGINT handling.

Add `context` field to `ApiError` and `withApiContext()` utility to attach human-readable operation context at call sites without verbose try/catch blocks. Drop internal "Platform API"/"Backend API" labels from the global error handler.

Bun's test runner doesn't fully clear process.exitCode when set to undefined, causing the test file to exit with code 1 despite all assertions passing.

brkalow · 2026-03-11T03:59:46Z

 .action(deploy);

-program.parse();
+function formatApiBody(body: string, verbose: boolean): string {


consider making this a method on ApiError

brkalow

Looks good, do you think there are any meaningful additions to AGENTS.md to be made to ensure this pattern is followed?

…ndling - Rename usageError/userAbort to throwUsageError/throwUserAbort to make the never-returning throw behavior explicit at call sites - Auto-append .md to Clerk docs URLs in agent mode so agents receive raw markdown instead of rendered HTML

wyattjoh · 2026-03-10T18:42:11Z

What

Introduce a typed error hierarchy (CliError, UserAbortError, ApiError, BapiError, PlapiError) in src/lib/errors.ts with standardized exit codes
Add a single top-level error handler in cli.ts that catches all typed errors and formats output consistently
Add --verbose flag for detailed API error output
Add SIGINT handler that exits with code 130
Add oxlint configuration (.oxlintrc.json)

Why

Error handling was scattered across every command — each had its own try/catch + console.error + process.exit with inconsistent formatting, exit codes, and messaging. This made it difficult to maintain consistent UX and meant every new command had to reimplement error handling. Centralizing it ensures uniform behavior and reduces per-command boilerplate.

How

Created src/lib/errors.ts with a class hierarchy: CliError for general CLI errors, ApiError (with BapiError/PlapiError subclasses) for HTTP failures, and UserAbortError for prompt cancellations. Helper functions usageError() and userAbort() provide ergonomic throwing.
Wrapped program.parseAsync() in a main() function with a centralized catch that dispatches on error type — clean exit for aborts, red-formatted messages for CLI errors, labeled API error details for API failures.
Updated all commands to throw typed errors instead of handling exits locally.
Updated all tests to assert on thrown errors rather than spying on process.exit.

AIE-626

Replace scattered try/catch + console.error + process.exit patterns with a typed error hierarchy (CliError, ApiError, BapiError, PlapiError, UserAbortError) and a single top-level error handler in cli.ts. Commands now throw typed errors instead of handling exits locally, making error behavior consistent and testable. Adds --verbose flag for detailed API error output and SIGINT handling.

Add `context` field to `ApiError` and `withApiContext()` utility to attach human-readable operation context at call sites without verbose try/catch blocks. Drop internal "Platform API"/"Backend API" labels from the global error handler.

Bun's test runner doesn't fully clear process.exitCode when set to undefined, causing the test file to exit with code 1 despite all assertions passing.

brkalow · 2026-03-11T03:59:46Z

 .action(deploy);

-program.parse();
+function formatApiBody(body: string, verbose: boolean): string {


consider making this a method on ApiError

brkalow

Looks good, do you think there are any meaningful additions to AGENTS.md to be made to ensure this pattern is followed?

…ndling - Rename usageError/userAbort to throwUsageError/throwUserAbort to make the never-returning throw behavior explicit at call sites - Auto-append .md to Clerk docs URLs in agent mode so agents receive raw markdown instead of rendered HTML

wyattjoh added 3 commits March 10, 2026 14:02

docs: add JSDoc comments to EXIT_CODE and CliErrorOptions
ed9de03

wyattjoh force-pushed the wyattjoh/errors branch from 7a9189c to ed9de03Compare March 10, 2026 20:03

fix(test): reset process.exitCode to 0 instead of undefined
c4391d6
Bun's test runner doesn't fully clear process.exitCode when set to undefined, causing the test file to exit with code 1 despite all assertions passing.

wyattjoh marked this pull request as ready for review March 10, 2026 20:19

kylemac requested review from Railly, brkalow and rafa-thayto March 10, 2026 20:26

brkalow reviewed Mar 11, 2026
View reviewed changes

brkalow approved these changes Mar 11, 2026
View reviewed changes

jfoshee reviewed Mar 11, 2026
View reviewed changes

Comment thread.oxlintrc.json

jfoshee approved these changes Mar 11, 2026
View reviewed changes

Comment threadsrc/lib/errors.ts Outdated

rafa-thayto reviewed Mar 11, 2026
View reviewed changes

Comment threadsrc/lib/errors.ts

wyattjoh added 2 commits March 11, 2026 10:17

docs: add error handling guidelines to CLAUDE.md
1ab0114

wyattjoh merged commit bb011ca into mainMar 11, 2026
2 checks passed

wyattjoh deleted the wyattjoh/errors branch March 11, 2026 16:24

rafa-thayto mentioned this pull request Mar 11, 2026
feat: add doctor command for project health checks #21
Merged
8 tasks

wyattjoh added 3 commits March 10, 2026 14:02

docs: add JSDoc comments to EXIT_CODE and CliErrorOptions
ed9de03

wyattjoh force-pushed the wyattjoh/errors branch from 7a9189c to ed9de03Compare March 10, 2026 20:03

fix(test): reset process.exitCode to 0 instead of undefined
c4391d6
Bun's test runner doesn't fully clear process.exitCode when set to undefined, causing the test file to exit with code 1 despite all assertions passing.

wyattjoh marked this pull request as ready for review March 10, 2026 20:19

kylemac requested review from Railly, brkalow and rafa-thayto March 10, 2026 20:26

brkalow reviewed Mar 11, 2026
View reviewed changes

brkalow approved these changes Mar 11, 2026
View reviewed changes

jfoshee reviewed Mar 11, 2026
View reviewed changes

Comment thread.oxlintrc.json

jfoshee approved these changes Mar 11, 2026
View reviewed changes

Comment threadsrc/lib/errors.ts Outdated

rafa-thayto reviewed Mar 11, 2026
View reviewed changes

Comment threadsrc/lib/errors.ts

wyattjoh added 2 commits March 11, 2026 10:17

docs: add error handling guidelines to CLAUDE.md
1ab0114

wyattjoh merged commit bb011ca into mainMar 11, 2026
2 checks passed

wyattjoh deleted the wyattjoh/errors branch March 11, 2026 16:24

rafa-thayto mentioned this pull request Mar 11, 2026
feat: add doctor command for project health checks #21
Merged
8 tasks

wyattjoh added 3 commits March 10, 2026 14:02

docs: add JSDoc comments to EXIT_CODE and CliErrorOptions
ed9de03

wyattjoh force-pushed the wyattjoh/errors branch from 7a9189c to ed9de03Compare March 10, 2026 20:03

fix(test): reset process.exitCode to 0 instead of undefined
c4391d6
Bun's test runner doesn't fully clear process.exitCode when set to undefined, causing the test file to exit with code 1 despite all assertions passing.

wyattjoh marked this pull request as ready for review March 10, 2026 20:19

kylemac requested review from Railly, brkalow and rafa-thayto March 10, 2026 20:26

brkalow reviewed Mar 11, 2026
View reviewed changes

brkalow approved these changes Mar 11, 2026
View reviewed changes

jfoshee reviewed Mar 11, 2026
View reviewed changes

Comment thread.oxlintrc.json

jfoshee approved these changes Mar 11, 2026
View reviewed changes

Comment threadsrc/lib/errors.ts Outdated

rafa-thayto reviewed Mar 11, 2026
View reviewed changes

Comment threadsrc/lib/errors.ts

wyattjoh added 2 commits March 11, 2026 10:17

docs: add error handling guidelines to CLAUDE.md
1ab0114

wyattjoh merged commit bb011ca into mainMar 11, 2026
2 checks passed

wyattjoh deleted the wyattjoh/errors branch March 11, 2026 16:24

rafa-thayto mentioned this pull request Mar 11, 2026
feat: add doctor command for project health checks #21
Merged
8 tasks

wyattjoh added 3 commits March 10, 2026 14:02

docs: add JSDoc comments to EXIT_CODE and CliErrorOptions
ed9de03

wyattjoh force-pushed the wyattjoh/errors branch from 7a9189c to ed9de03Compare March 10, 2026 20:03

fix(test): reset process.exitCode to 0 instead of undefined
c4391d6
Bun's test runner doesn't fully clear process.exitCode when set to undefined, causing the test file to exit with code 1 despite all assertions passing.

wyattjoh marked this pull request as ready for review March 10, 2026 20:19

kylemac requested review from Railly, brkalow and rafa-thayto March 10, 2026 20:26

brkalow reviewed Mar 11, 2026
View reviewed changes

brkalow approved these changes Mar 11, 2026
View reviewed changes

jfoshee reviewed Mar 11, 2026
View reviewed changes

Comment thread.oxlintrc.json

jfoshee approved these changes Mar 11, 2026
View reviewed changes

Comment threadsrc/lib/errors.ts Outdated

rafa-thayto reviewed Mar 11, 2026
View reviewed changes

Comment threadsrc/lib/errors.ts

wyattjoh added 2 commits March 11, 2026 10:17

docs: add error handling guidelines to CLAUDE.md
1ab0114

wyattjoh merged commit bb011ca into mainMar 11, 2026
2 checks passed

wyattjoh deleted the wyattjoh/errors branch March 11, 2026 16:24

rafa-thayto mentioned this pull request Mar 11, 2026
feat: add doctor command for project health checks #21
Merged
8 tasks

wyattjoh added 3 commits March 10, 2026 14:02

docs: add JSDoc comments to EXIT_CODE and CliErrorOptions
ed9de03

wyattjoh force-pushed the wyattjoh/errors branch from 7a9189c to ed9de03Compare March 10, 2026 20:03

fix(test): reset process.exitCode to 0 instead of undefined
c4391d6
Bun's test runner doesn't fully clear process.exitCode when set to undefined, causing the test file to exit with code 1 despite all assertions passing.

wyattjoh marked this pull request as ready for review March 10, 2026 20:19

kylemac requested review from Railly, brkalow and rafa-thayto March 10, 2026 20:26

brkalow reviewed Mar 11, 2026
View reviewed changes

brkalow approved these changes Mar 11, 2026
View reviewed changes

jfoshee reviewed Mar 11, 2026
View reviewed changes

Comment thread.oxlintrc.json

jfoshee approved these changes Mar 11, 2026
View reviewed changes

Comment threadsrc/lib/errors.ts Outdated

rafa-thayto reviewed Mar 11, 2026
View reviewed changes

Comment threadsrc/lib/errors.ts

wyattjoh added 2 commits March 11, 2026 10:17

docs: add error handling guidelines to CLAUDE.md
1ab0114

wyattjoh merged commit bb011ca into mainMar 11, 2026
2 checks passed

wyattjoh deleted the wyattjoh/errors branch March 11, 2026 16:24

rafa-thayto mentioned this pull request Mar 11, 2026
feat: add doctor command for project health checks #21
Merged
8 tasks

wyattjoh added 3 commits March 10, 2026 14:02

docs: add JSDoc comments to EXIT_CODE and CliErrorOptions
ed9de03

wyattjoh force-pushed the wyattjoh/errors branch from 7a9189c to ed9de03Compare March 10, 2026 20:03

fix(test): reset process.exitCode to 0 instead of undefined
c4391d6
Bun's test runner doesn't fully clear process.exitCode when set to undefined, causing the test file to exit with code 1 despite all assertions passing.

wyattjoh marked this pull request as ready for review March 10, 2026 20:19

kylemac requested review from Railly, brkalow and rafa-thayto March 10, 2026 20:26

brkalow reviewed Mar 11, 2026
View reviewed changes

brkalow approved these changes Mar 11, 2026
View reviewed changes

jfoshee reviewed Mar 11, 2026
View reviewed changes

Comment thread.oxlintrc.json

jfoshee approved these changes Mar 11, 2026
View reviewed changes

Comment threadsrc/lib/errors.ts Outdated

rafa-thayto reviewed Mar 11, 2026
View reviewed changes

Comment threadsrc/lib/errors.ts

wyattjoh added 2 commits March 11, 2026 10:17

docs: add error handling guidelines to CLAUDE.md
1ab0114

wyattjoh merged commit bb011ca into mainMar 11, 2026
2 checks passed

wyattjoh deleted the wyattjoh/errors branch March 11, 2026 16:24

rafa-thayto mentioned this pull request Mar 11, 2026
feat: add doctor command for project health checks #21
Merged
8 tasks

wyattjoh added 3 commits March 10, 2026 14:02

docs: add JSDoc comments to EXIT_CODE and CliErrorOptions
ed9de03

wyattjoh force-pushed the wyattjoh/errors branch from 7a9189c to ed9de03Compare March 10, 2026 20:03

fix(test): reset process.exitCode to 0 instead of undefined
c4391d6
Bun's test runner doesn't fully clear process.exitCode when set to undefined, causing the test file to exit with code 1 despite all assertions passing.

wyattjoh marked this pull request as ready for review March 10, 2026 20:19

kylemac requested review from Railly, brkalow and rafa-thayto March 10, 2026 20:26

brkalow reviewed Mar 11, 2026
View reviewed changes

brkalow approved these changes Mar 11, 2026
View reviewed changes

jfoshee reviewed Mar 11, 2026
View reviewed changes

Comment thread.oxlintrc.json

jfoshee approved these changes Mar 11, 2026
View reviewed changes

Comment threadsrc/lib/errors.ts Outdated

rafa-thayto reviewed Mar 11, 2026
View reviewed changes

Comment threadsrc/lib/errors.ts

wyattjoh added 2 commits March 11, 2026 10:17

docs: add error handling guidelines to CLAUDE.md
1ab0114

wyattjoh merged commit bb011ca into mainMar 11, 2026
2 checks passed

wyattjoh deleted the wyattjoh/errors branch March 11, 2026 16:24

rafa-thayto mentioned this pull request Mar 11, 2026
feat: add doctor command for project health checks #21
Merged
8 tasks

wyattjoh added 3 commits March 10, 2026 14:02

docs: add JSDoc comments to EXIT_CODE and CliErrorOptions
ed9de03

wyattjoh force-pushed the wyattjoh/errors branch from 7a9189c to ed9de03Compare March 10, 2026 20:03

fix(test): reset process.exitCode to 0 instead of undefined
c4391d6
Bun's test runner doesn't fully clear process.exitCode when set to undefined, causing the test file to exit with code 1 despite all assertions passing.

wyattjoh marked this pull request as ready for review March 10, 2026 20:19

kylemac requested review from Railly, brkalow and rafa-thayto March 10, 2026 20:26

brkalow reviewed Mar 11, 2026
View reviewed changes

brkalow approved these changes Mar 11, 2026
View reviewed changes

jfoshee reviewed Mar 11, 2026
View reviewed changes

Comment thread.oxlintrc.json

jfoshee approved these changes Mar 11, 2026
View reviewed changes

Comment threadsrc/lib/errors.ts Outdated

rafa-thayto reviewed Mar 11, 2026
View reviewed changes

Comment threadsrc/lib/errors.ts

wyattjoh added 2 commits March 11, 2026 10:17

docs: add error handling guidelines to CLAUDE.md
1ab0114

wyattjoh merged commit bb011ca into mainMar 11, 2026
2 checks passed

wyattjoh deleted the wyattjoh/errors branch March 11, 2026 16:24

rafa-thayto mentioned this pull request Mar 11, 2026
feat: add doctor command for project health checks #21
Merged
8 tasks

Uh oh!

Conversation

wyattjoh commented Mar 10, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What

Why

How

Uh oh!

brkalowMar 11, 2026

Choose a reason for hiding this comment

Uh oh!

brkalow left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Conversation

wyattjoh commented Mar 10, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What

Why

How

Uh oh!

brkalowMar 11, 2026

Choose a reason for hiding this comment

Uh oh!

brkalow left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Conversation

wyattjoh commented Mar 10, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What

Why

How

Uh oh!

brkalowMar 11, 2026

Choose a reason for hiding this comment

Uh oh!

brkalow left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Conversation

wyattjoh commented Mar 10, 2026•
edited
Loading

wyattjoh commented Mar 10, 2026•
edited
Loading

wyattjoh commented Mar 10, 2026•
edited
Loading

wyattjoh commented Mar 10, 2026•
edited
Loading

wyattjoh commented Mar 10, 2026•
edited
Loading