---

name: try-error-handling description: Error handling with @julian-i/try-error. Wrap throwable code with tryPromise (async) or tryThrow (sync). Forces reflection on error types, handling location, audience, and recovery.

Error Handling with @julian-i/try-error

Wrap all throwable operations. Before handling, ask:

1. What errors? — Use context7 MCP to check library docs
2. Handle here or propagate? — Can you recover, or should caller decide?
3. Who's the audience? — End user (friendly) or developer (detailed)?
4. Recovery strategy? — Retry, fallback, degrade, or fail fast?

Usage

Copyimport { tryPromise, tryThrow } from '@julian-i/try-error';

// Async: fetch, db, auth, file I/O
const [data, error] = await tryPromise(fetch('/api/users'));

// Sync: JSON.parse, validation, transforms
const [parsed, error] = tryThrow(() => JSON.parse(raw));

if (error) {
  // Handle based on error type and audience
}

Quick Reference

References

• Error types by library: references/error-sources.md — Prisma, Drizzle, better-auth, Zod, fetch, Stripe
• SvelteKit patterns: references/sveltekit-patterns.md — actions, load, endpoints, hooks
• Next.js patterns: references/nextjs-patterns.md — server actions, route handlers, middleware
• TypeScript patterns: references/typescript-patterns.md — services, utilities, testing