data in createError() is missing in response

[ijkml]

Environment

node: 22.6.0
bun: 1.1.33

Reproduction

Run example from repo:

h3/examples/errors.ts

Lines 20 to 25 in 7324eee

	throw createError({
	status: 500,
	message: "Fatal error",
	fatal: true,
	data: { foo: "bar" },
	});

(log below)

Describe the bug

It's currently not possible to use err.data to pass additional data to client-side.

Additional context

#823 (comment)

Logs

{
  "url": "/devices/lol/",
  "statusCode": 500,
  "statusMessage": "",
  "message": "Fatal error",
  "stack": [
    "at createError (./node_modules/h3/dist/index.mjs:78:15)",
    "at badParamError (./.nitro/dev/index.mjs:934:9)",
    "at Object.handler (./.nitro/dev/index.mjs:992:11)",
    "at ./node_modules/h3/dist/index.mjs:1906:43",
    "at process.processTicksAndRejections (node:internal/process/task_queues:95:5)",
    "at async Object.handler (./node_modules/h3/dist/index.mjs:1978:19)",
    "at async Server.toNodeHandle (./node_modules/h3/dist/index.mjs:2270:7)"
  ]
}

[iiio2]

@ijkml , according to h3 docs, it is recommended to throw errors instead of returning them using createError utility. You may check and try with it (https://h3.unjs.io/guide/event-handler#responses-types).

[nick-w-nick]

@pi0 Can we get some clarification as to whether errors should be thrown via throw new Error() or if it is preferred to throw createError() instead? createError can be useful for setting a custom status code, but I can see why it may not be preferred since it isn't as framework-agnostic. The docs do say to prefer throwing actual Error's, but just wanted to clarify if that is the same planned behavior for V2.