@1gr14/error0

One typed Error class for your whole app — coerce any thrown value into it, let typed fields flow through cause chains, and serialize it safely across the wire.

A project deserves one error class — a single type that any thrown value can be coerced into, that carries errors from your server to your client, and that knows how to serialize itself two ways: privately for your logs and publicly for untrusted clients. error0 is that class, built as a small builder: you start from Error0 and extend it with typed fields — inline, or with ready-made plugins.

Errors travel. You throw in one layer and catch in another — sometimes it's your error, sometimes a native Error, sometimes an Axios or Zod error, sometimes just a string. error0 turns any of them into one typed class you control. Its fields flow up through cause chains, and the whole error serializes to JSON and back — so it survives a trip across a process, a queue, or the network.

import { Error0 } from '@1gr14/error0'
import { statusPlugin } from '@1gr14/error0/plugins/status'
import { codePlugin } from '@1gr14/error0/plugins/code'

// One error class for the whole app — compose the fields you need.
export const AppError = Error0.mark('AppError')
  .use(statusPlugin({ transport: 'public' })) // a ready-made plugin: typed `status`
  .use(codePlugin({ codes: ['UNAUTHORIZED', 'FORBIDDEN'] as const })) // and a typed `code`
  .use('prop', 'requestId', { init: (id: string) => id }) // or any field you want, inline

// Type the instance, the way you would with `class AppError extends Error`.
export type AppError = InstanceType<typeof AppError>

// Build with typed fields — from a plugin or your own.
const inner = new AppError('Token expired', {
  status: 401,
  code: 'UNAUTHORIZED',
  requestId: 'req_42',
})
inner.requestId // 'req_42'  ← your own inline field, typed string | undefined

// Wrap a cause — fields flow up the chain.
const outer = new AppError('Request failed', { cause: inner })
outer.status // 401  ← flowed up from the inner cause
outer.flow('status') // [undefined, 401]  — the value at each level of the chain

// Coerce anything at a boundary, then serialize a client-safe payload.
const json = AppError.serializePublic(outer) // { message, status } — no code, no stack

// ...and rebuild a real AppError on the other side.
const restored = AppError.from(json)
restored.status // 401  ← survived the round-trip

Install

bun add @1gr14/error0
# or: npm install / pnpm add / yarn add

Bun 1+ or Node.js 20+. ESM only.

Give your errors typed fields

A bare message isn't enough. You want an HTTP status, a machine-readable code, whatever your app needs. Add a field with .use('prop', name, options) — the same call the hero used inline. A field is up to four small functions, and only the first is required:

const AppError = Error0.use('prop', 'status', {
  init: (input: number) => input,
  resolve: ({ flow }) => flow.find(Boolean),
  serialize: ({ resolved }) => resolved,
  deserialize: ({ value }) => (typeof value === 'number' ? value : undefined),
})

const err = new AppError('User not found', { status: 404 })
err.status // 404  ← typed as number | undefined

Each function does one job. Here's what each one is for.

init — declare and accept the input

init types the value you pass in. Writing (input: number) is what makes new AppError('...', { status }) expect a number — the input type comes straight from init's first argument. Its return type is what gets stored, so you can transform on the way in, not just pass the value through:

init: (input: number) => input // status is a number
init: (name: 'on' | 'off') => name === 'on' // accept a name, store a boolean

A field is never required on input — init types the value when you pass one, it never forces you to. That's the rule that lets from() turn any error into yours.

Skip init and the field drops out of the constructor — you can't pass it at all. It becomes a computed field, filled only from a cause or an adapt hook, and its type then comes from what resolve returns:

// no init → not accepted in `new AppError(...)`, derived instead
const AppError = Error0.use('prop', 'fingerprint', {
  resolve: ({ error }) => `${error.name}:${error.message}`, // err.fingerprint is a string
})

resolve — compute the value you read

resolve decides what err.status returns. It sees this field's value at every level of the cause chain and returns the one to expose:

• flow — this field's value on each link is() recognizes as yours, nearest first. Foreign links (a native Error, a ZodError) are skipped — they carry none of your fields. flow.find(Boolean) means "the first status anyone set".
• own — just this error's own value, before any chain logic.
• error — the error instance itself (call error.causes() to walk the whole chain, foreign links included).

Omit resolve (or pass resolve: false) and the field just returns its own value, ignoring causes. Return a constant and every error reports it. It's the same lever the chain-merging plugins (tags, meta, headers) pull — more on the flow in the next section.

serialize — write the value to JSON

serialize is the field's half of the JSON boundary, going out. Return the value to put in the JSON, or undefined to drop the field. It receives { own, flow, resolved, error, isPublic } — most often you just return resolved. The isPublic flag is how a field shows in the public output or only the private one (see Public and private serialization). Pass serialize: false to keep the field server-only — it never crosses the wire.

deserialize — read the value back from JSON

deserialize is the other half, coming back in: it turns the raw JSON value into your field when from() rebuilds the error. It receives { value, record } — value is the raw field, record is the whole serialized object if you need a sibling. Validate as you read: typeof value === 'number' ? value : undefined drops anything that isn't a number, so a malformed payload can't smuggle in a wrong type. Pass deserialize: false and the field is never read back.

Fields flow through cause chains

Here's why resolve takes a flow. When you wrap an error, the inner error's status shouldn't vanish. flow is this field's value on each error in the chain that is() recognizes as yours, nearest first — so flow.find(Boolean) means "the first status anyone set":

const inner = new AppError('DB unreachable', { status: 503 })
const outer = new AppError('Could not load user', { cause: inner })

outer.status // 503  ← flowed up from `inner`
outer.flow('status') // [undefined, 503]  — outer set nothing, inner set 503
outer.resolve() // { status: 503 } — every field resolved into one object
inner.own // { status: 503 } — the raw fields set on an error, before resolve runs

Only links that are your error feed the flow — a native Error, a ZodError, or any other foreign cause is skipped, because it carries no fields of yours. The two causes() helpers make the line explicit:

const outer = new AppError('Failed', { cause: new TypeError('boom') })

outer.causes() // [outer, TypeError]  — every link, foreign ones included
outer.causes(true) // [outer]         — only links that are your error
Error0.causes(outer) // the same walk, also available as a static

So flow walks causes(true); reach for causes() when you want the raw chain, foreign errors and all. Either walk is capped at Error0.MAX_CAUSES_DEPTH (default 99) to guard against cycles.

Any error becomes your error

So far every error here is one you built. But most errors you catch came from somewhere else — a native Error, an Axios failure, a string someone threw. Those become your error too. Error0.from() gives you a typed error you can trust, every time:

import { Error0 } from '@1gr14/error0'

Error0.from(new Error('boom')) // wraps the native error, keeps it as `cause`
Error0.from('boom') // wraps the string
Error0.from({ message: 'boom' }) // rebuilds from a serialized object
Error0.from(error0Instance) // already an Error0 → returned as-is

try {
  await doStuff()
} catch (e) {
  throw Error0.from(e) // always an Error0, original preserved as `cause`
}

This works because of one design rule: every field is optional on input. No field is ever required, so any error can become an Error0 — there's nothing that could be "missing".

Error0 is a real subclass of Error, so everything you expect still works:

const err = new Error0('nope')
err instanceof Error0 // true
err instanceof Error // true
err.message // 'nope'
err.stack // present

One class, fields not subclasses

You usually want a single AppError for the whole app — not a DbError, ApiError, ValidationError zoo. Model the differences as fields, not classes. A field can hold anything — a whole object, not just a primitive — and you choose whether it crosses the wire.

// Don't reach for a separate DbError — add a field holding the raw driver error.
const AppError = Error0.use('prop', 'dbError', {
  init: (error: PostgresError) => error, // the input can be a whole object
  resolve: ({ flow }) => flow.find(Boolean),
  serialize: false, // keep it server-side; never send it to a client
  deserialize: false,
})

const err = new AppError('Query failed', { dbError: pgError })
err.dbError // the full driver error, typed — for your logs
AppError.serialize(err) // { message } — `dbError` never crosses the wire

But you usually won't set dbError by hand — you catch an unknown and don't even know it is a database error. So pair the field with an adapt hook: it runs on every new error (including the ones from() builds), looks at the cause, and routes a driver error into the field for you.

const AppError = Error0.use('prop', 'dbError', {
  init: (error: PostgresError) => error,
  resolve: ({ flow }) => flow.find(Boolean),
  serialize: false,
  deserialize: false,
}).use('adapt', (error) => {
  // caught something unknown — if a driver error is underneath, capture it
  if (error.cause instanceof PostgresError) {
    return { dbError: error.cause } // returned fields get assigned to the error
  }
})

// now just wrap whatever you caught — the field fills itself in
const err = AppError.from(pgError) // a PostgresError that bubbled up
err.dbError // the driver error, captured automatically — still server-only

That's the payoff of one class: you catch once, at the boundary, without knowing the origin, and the error sorts itself into the right fields. (More on adapt in Adapt foreign errors at construction.)

One class to catch, one is(), one serialize contract — every concern lives as a typed field on it.

Add behavior with methods

Fields are data. You'll also want behavior — a question you ask an error often. Add a method:

const AppError = Error0.use('prop', 'status', {
  init: (input: number) => input,
  resolve: ({ flow }) => flow.find(Boolean),
}).use(
  'method',
  'isStatus',
  (error, expected: number) => error.status === expected,
)

const err = new AppError('Forbidden', { status: 403 })
err.isStatus(403) // true

// Every method is also a static that runs `from()` on its first argument —
// so it works on anything: an AppError, a serialized object, or a native error.
AppError.isStatus(err, 403) // true

Adapt foreign errors at construction

An adapt hook runs on every new error — including the ones from() builds out of foreign errors. It gets the live error, so it can read the cause, return fields to set them, and mutate native parts like message directly. This is where you teach Error0 to understand the rest of the world.

Turn a ZodError into a clean 422 — status from the return value, message from the error's first issue:

import { z } from 'zod'

const ApiError = AppError.use('adapt', (error) => {
  if (error.cause instanceof z.ZodError) {
    error.message = error.cause.issues[0]?.message ?? error.message // mutate native parts
    return { status: 422 } // returned fields are assigned to the error
  }
})

const err = ApiError.from(zodError) // a ZodError you caught upstream
err.message // 'Invalid email address'  ← first Zod issue
err.status // 422

Two levers: return an object to set typed fields, and mutate the error for its native parts (message, stack). To set fields on an error you already have, use err.assign({ status: 500 }) (returns the same error) or the static AppError.assign(error, props).

Public and private serialization

This is the payoff, and the reason error0 exists: serialize to plain JSON, ship it anywhere, rebuild a real typed error on the other side. But the two audiences are different. Some fields are for your logs, not your users — so there are two named outputs:

• serializePublic() — what an untrusted client may see.
• serializePrivate() — the full view, for trusted consumers (logs, dev tooling).

Both are thin sugar over serialize(isPublic). Each bundled plugin takes a transport option to pick its audience:

const AppError = Error0.use(statusPlugin({ transport: 'public' })) // visible to clients
  .use(codePlugin()) // transport: 'private' by default

const err = new AppError('Nope', { status: 403, code: 'FORBIDDEN' })

err.serializePublic() // { message, status }          ← no code, no stack
err.serializePrivate() // { message, status, code, stack }

// Send the public payload to the browser; log the private one on the server.
const back = AppError.from(err.serializePrivate()) // a real AppError again
back.code // 'FORBIDDEN'  ← survived the round-trip

transport is just a default for the field's own serialize gate: 'public' puts the field in both outputs, 'private' only in serializePrivate(), 'none' never serializes it. There's no magic — it's the field's serialize function, which gets a call-time isPublic flag and returns the value to keep, or undefined to drop it entirely:

// the exact gate every bundled plugin uses, given `transport`
serialize: ({ resolved, isPublic }) => {
  if (transport === 'none' || (transport === 'private' && isPublic))
    return undefined
  return resolved // otherwise, put the value in the JSON
}

Write your own serialize and you decide exactly what crosses the wire — mask a value, round it, or drop it. (err.round() / Error0.round(error) is from(serialize(error)) in one call — handy in tests to assert a value survives the trip.)

Reserved fields: message and stack

message and stack are built into Error, so adding them as props throws. To change how they serialize, use their own hooks instead — .use('message', { serialize }) and .use('stack', { serialize }):

// keep the stack out of every serialized output
const AppError = Error0.use('stack', { serialize: () => undefined })

The bundled stackPlugin, messageMergePlugin, and stackMergePlugin are built on exactly these hooks.

Bundle fields into reusable plugins

Defining status inline once is fine. Defining it in every service is not. Wrap it in a plugin with Error0.plugin() and reuse it everywhere:

export const statusPlugin = () =>
  Error0.plugin().prop('status', {
    init: (input: number) => input,
    resolve: ({ flow }) => flow.find(Boolean),
    serialize: ({ resolved }) => resolved,
    deserialize: ({ value }) => (typeof value === 'number' ? value : undefined),
  })

const AppError = Error0.use(statusPlugin())

A plugin builder mirrors the inline API, one method per kind:

• .prop(name, options) — a typed field (same options as .use('prop', …)).
• .method(name, fn) — an instance method.
• .adapt(fn) — a hook that runs on every new error.
• .cause(value) / .stack(value) / .message(value) — customize how those reserved parts serialize and rebuild.
• .use(plugin) — merge another plugin in, so plugins can compose plugins.

Each .use(...) on Error0 returns a new class with the previous fields plus the new ones, all typed. Stack as many as you like:

const AppError = Error0.use(statusPlugin()).use(codePlugin())
const ApiError = AppError.use(tagsPlugin()) // keeps status + code, adds tags

Tell error classes apart: is and mark

One AppError is usually enough — model the rest as fields (see One class, fields not subclasses). But if you do split into several classes, is() tells them apart and narrows the type inside the branch:

const ApiError = Error0.use(statusPlugin())
const DbError = Error0.use(codePlugin())

try {
  await handler()
} catch (e) {
  if (ApiError.is(e)) {
    e.status // typed — `e` is an ApiError here
  } else if (DbError.is(e)) {
    e.code // typed — `e` is a DbError here
  }
}

is() checks instanceof under the hood, so distinct classes stay distinct — no setup needed. But instanceof breaks when the same class ships in two bundles (a server build and a client build) — the two copies are different classes. mark brands a class with a stable id that is() checks instead of the prototype chain, so recognition survives that boundary:

const ApiError = Error0.mark('myapp/api').use(statusPlugin())

ApiError.is(err) // matched by brand, even where `instanceof` would fail

Use a string or a Symbol.for('...') as the mark — both are stable across bundles. Never a plain Symbol('...'): it's unique per bundle. A string mark also becomes err.name. Give several classes the same mark and is() treats them as one family.

Better stack traces in dev

Bundlers (Vite, tsx, esbuild) rewrite your code, so stack traces point at compiled output instead of your source. error0 calls an optional global hook on every error and each of its causes at construction, so a tool can remap the stack. It's a no-op when NODE_ENV === 'production'.

Wire it once — for example, with Vite's SSR fixer:

// dev setup only
globalThis.__ERROR0_FIX_STACKTRACE__ = (error) =>
  viteDevServer.ssrFixStacktrace(error)

Now every Error0, and each error in its cause chain, gets readable, source-mapped stack traces in development.

Ready-made plugins

The common fields are already written. Import only what you use, each from its own path under @1gr14/error0/plugins/* (tree-shakeable). Every plugin is a function you call and pass to .use().

Each one is a small, readable function built on the same hooks you just saw — the source link under each is worth opening, and it's the best template for writing your own.

Each field plugin below accepts a transport option — 'public', 'private' (default), or 'none' — that decides whether its field shows up in serializePublic(), only in serializePrivate(), or never.

Typed-field plugins

statusPlugin — an HTTP-style status

src/plugins/status.ts

import { statusPlugin } from '@1gr14/error0/plugins/status'

const AppError = Error0.use(statusPlugin({ transport: 'public' }))
const err = new AppError('Not found', { status: 404 })
err.status // 404

Pass a statuses map to accept a status by name, and strict to reject any number that isn't in it:

const AppError = Error0.use(
  statusPlugin({ statuses: { NOT_FOUND: 404, FORBIDDEN: 403 }, strict: true }),
)
const err = new AppError('x', { status: 'NOT_FOUND' })
err.status // 404

codePlugin — a machine-readable code

src/plugins/code.ts

Pass codes to lock the field to a typed union; only those codes type-check.

import { codePlugin } from '@1gr14/error0/plugins/code'

const AppError = Error0.use(
  codePlugin({ codes: ['NOT_FOUND', 'BAD_REQUEST'] as const }),
)
new AppError('x', { code: 'NOT_FOUND' }) // 'NOPE' would be a type error

codeStatusPlugin — code and status together

src/plugins/code-status.ts

A { CODE: status } map adds both fields and auto-fills the status from the code (unless you pass a status yourself). Use true for a code that has no fixed status.

import { codeStatusPlugin } from '@1gr14/error0/plugins/code-status'

const AppError = Error0.use(
  codeStatusPlugin({
    codes: { NOT_FOUND: 404, FORBIDDEN: 403, RATE_LIMITED: true },
  }),
)
const err = new AppError('x', { code: 'NOT_FOUND' })
err.status // 404 — filled from the map

tagsPlugin — a tags set + hasTag()

src/plugins/tags.ts

Tags merge and dedupe across the whole cause chain.

import { tagsPlugin } from '@1gr14/error0/plugins/tags'

const AppError = Error0.use(
  tagsPlugin({ tags: ['retryable', 'user-error'] as const }),
)
const err = new AppError('x', { tags: ['user-error'] })

err.hasTag('user-error') // true
err.hasTag(['retryable', 'user-error'], 'some') // true — policy 'every' (default) or 'some'

Options: tags (whitelist), strict (default true — drops unknown tags when deserializing), transport.

metaPlugin — free-form meta

src/plugins/meta.ts

JSON-safe metadata. Wrap one error in another and the meta of the whole chain merges into one object — nearer errors win on a key conflict.

import { metaPlugin } from '@1gr14/error0/plugins/meta'

const AppError = Error0.use(metaPlugin())

const inner = new AppError('DB down', { meta: { userId: 7, attempt: 1 } })
const outer = new AppError('Load failed', {
  cause: inner,
  meta: { attempt: 2 },
})

outer.meta // { userId: 7, attempt: 2 } — merged up the chain; outer wins on `attempt`

expectedPlugin — an expected flag + isExpected()

src/plugins/expected.ts

Mark errors that are part of normal flow (a 404, a validation miss) so you don't log them as crashes. A single expected: false anywhere in the chain wins.

import { expectedPlugin } from '@1gr14/error0/plugins/expected'

const AppError = Error0.use(expectedPlugin())
const err = new AppError('Not found', { expected: true })
err.isExpected() // true

Options: transport, and override to force the verdict from the error itself.

headersPlugin — HTTP headers

src/plugins/headers.ts

Headers to attach to a response, merged across the chain. Never serialized.

import { headersPlugin } from '@1gr14/error0/plugins/headers'

const AppError = Error0.use(headersPlugin())
const err = new AppError('Rate limited', { headers: { 'Retry-After': '30' } })
err.headers

responsePlugin — a Response object

src/plugins/response.ts

Carry a fetch Response with the error (to read its body later, say). Never serialized.

import { responsePlugin } from '@1gr14/error0/plugins/response'

const AppError = Error0.use(responsePlugin())
const err = new AppError('Upstream failed', { response })
err.response // the Response

redirectPlugin — a navigation redirect (for point0)

src/plugins/point0-redirect.ts

Attach a redirect to an error. Built for point0; a RedirectTask thrown as a cause is adopted automatically.

import { redirectPlugin } from '@1gr14/error0/plugins/point0-redirect'

const AppError = Error0.use(redirectPlugin())
const err = new AppError('Go to login', {
  redirect: { to: '/login', status: 302 },
})
err.redirect

Serialization & adapt plugins

These don't add a field of their own — they shape how the error serializes or adapts.

causePlugin — carry the cause chain across the wire

src/plugins/cause.ts

By default a .cause isn't serialized — it can't always survive JSON. causePlugin makes it travel: nested Error0 causes are rebuilt by from(), and foreign errors (Zod, Axios, …) are kept as { name, message, stack } with their own chain walked (cycle- and depth-guarded).

import { causePlugin } from '@1gr14/error0/plugins/cause'

const AppError = Error0.use(causePlugin())
// serializePrivate() now includes `cause`, and from() rebuilds it

Option: transport (default 'private' — kept out of serializePublic()).

stackPlugin — the stack policy, as a plugin

src/plugins/stack.ts

The core already keeps the stack in serializePrivate() only; this plugin spells that policy out and makes it switchable. transport: 'private' (default) keeps the stack out of public output, 'public' sends it to clients too, 'none' strips it everywhere.

import { stackPlugin } from '@1gr14/error0/plugins/stack'

const AppError = Error0.use(stackPlugin({ transport: 'none' })) // never serialize the stack

messageMergePlugin — one message from the whole chain

src/plugins/message-merge.ts

On serialize, joins every error's message down the cause chain into one string.

import { messageMergePlugin } from '@1gr14/error0/plugins/message-merge'

const AppError = Error0.use(messageMergePlugin())
// serialized message: 'Outer: inner: root cause'  — joined with ': '

Options: delimiter (default ': '), fallback (default 'Unknown error').

stackMergePlugin — one stack from the whole chain

src/plugins/stack-merge.ts

Like messageMergePlugin, but joins the stacks of every cause.

import { stackMergePlugin } from '@1gr14/error0/plugins/stack-merge'

const AppError = Error0.use(stackMergePlugin())

Options: transport (default 'private'), delimiter (default '\n').

flatOriginalPlugin — adopt a native cause's message and stack

src/plugins/flat-original.ts

When you wrap a plain native Error, this hoists its message and stack onto your Error0 (and unwraps the cause), so the top error reads like the original instead of a generic wrapper.

import { flatOriginalPlugin } from '@1gr14/error0/plugins/flat-original'

const AppError = Error0.use(flatOriginalPlugin())
const err = AppError.from(new Error('socket hang up'))
err.message // 'socket hang up'

Option: prefix, prepended to the adopted message.

Community

Questions, bugs, or want to hang with other builders? Join the 1gr14 community — one hub for all our open-source projects, this one included. Get help, share what you built, or just say hi: 1gr14.dev/#community

Contributing

Issues and PRs welcome. See CONTRIBUTING.md and the Code of Conduct. Commits follow Conventional Commits. Security reports: SECURITY.md.

License

MIT

Made by 1gr14, driven by community