ZerospinError

Create structured errors with stable codes, human messages, and optional metadata.

Quick patterns

• •Prefer full form with code, message, and cause when wrapping.
• •Use the short form only for trivial cases: new ZerospinError('some-code').
• •Return errors from Effect.gen with return yield* new ZerospinError(...).

const error = new ZerospinError({
 code: 'failed-to-fetch',
 message: 'Failed to fetch data',
 cause: originalError,
 extra: { url },
 status: 502,
});

Rules

• •Use a stable, kebab-case code string; never include dynamic data in the code.
• •Keep message human-readable and specific to the failure.
• •Always attach the original cause when wrapping another error.
• •Use extra for structured metadata (ids, inputs, context), not for free-form text.
• •Use status only for HTTP-facing errors.

Effect usage

Return it don't throw it, duh

const res = yield* Effect.promise(() => fetch('/api/data'));
if (res.status === 404) {
 return yield* new ZerospinError({
  code: 'resource-not-found',
  message: 'Resource not found',
 });
}

Working with promises - mapError!

const parsed = Effect.promise(() => res.json()).pipe(
 Effect.mapError((error) => {
  return new ZerospinError({
   code: 'failed-to-parse-json',
   message: 'Failed to parse JSON',
   cause: error,
  });
 })
);

Effect.fn

Catch all

const safe = effect.pipe(
 Effect.catchAll((error) => {
  return new ZerospinError({
   code: 'operation-failed',
   message: error.message,
   cause: error,
  });
 })
);