Description

When using this router with Next.js, which relies on the statusCode property (and not status), errors incorrectly default to a 500 status because Next.js does not read the status property.

In Express 4.x, both status and statusCode were set on error objects. However, in this version, only status is set. This causes compatibility issues with Next.js, resulting in incorrect HTTP status codes being returned.

This fix ensures that the statusCode property is also set on error objects in layer.js, restoring compatibility with Next.js and preventing erroneous 500 responses.