Run & review this pull request in StackBlitz Codeflow.

statusCode is used consistently in Nitro, e.g.:

https://github.com/unjs/nitro/blob/d20ffcbd16fc4003b774445e1a01e698c2bb078a/src/runtime/internal/task.ts#L37-L49

The move from statusMessage -> message looks good.

What do you think @pi0?

If i'm not wrong statusMessage was Node.js flavor.

status and statusText are Web Response props. i would try to adopt them consistently everywhere.

~> unjs/h3#767

Contra my previous message, we should not update statusMessage -> message. It should be statusMessage -> statusText. message is a separate field that governs the content of the body.

I'm a little reluctant to update the docs yet as the type of the error returned from createError still has statusCode and statusMessage fields, which is possibly just confusing for people. (For example, an error thrown with { status: 400 } would have { statusCode: 400 } and no status property.)

statusCode and status would be used in different places. (Still required by Nitro render response, for example.) And the error object provided by Nuxt in error.vue and elsewhere still expects those properties. Likely we'd need to implement backwards compatibility with a getter in h3/nuxt.

As a result, I think we need to defer this PR for now. Depending on what we do in h3, we might still merge it in time for 4.x. What do you think @pi0?