Log route for exceptions

Describe the feature

I am currently using Nuxt to write an application. As it is almost impossible to check for every eventuality during development there are sometimes exception logged on production. However, as everything is bundled, the stack traces are not really useful and do not give any hint as to which route was causing the problem.

In those cases it would greatly simplify troubleshooting if some information about the request is also logged for exceptions.

In some cases it is possible to find the handler file ( ./.output/server/chunks/foobar.get.mjs) listed as part of the stack trace though that is not always the case. For example I have to error messages [nuxt] [request error] [unhandled] [500] The first argument must be of type string or an instance of Buffer, ArrayBuffer, or Array or an Array-like Object. Received an instance of URLSearchParams and [nuxt] [request error] [unhandled] [500] Cannot set headers after they are sent to the client where I do not know from which handler they originate. Therefore I am also not sure if this might be my fault or something within Nuxt which is failing - and I have no good way to create a reproducible example to figure that out and maybe raise a proper issue here.

Additional information

• Would you be willing to help implement this feature?

The issue identifies production request exceptions and generated handler paths such as ./.output/server/chunks/foobar.get.mjs. Start by locating Nitro’s request-error logging path and determine how the originating route can be retained; done means exception logs identify the request route without relying on bundled stack traces, including the two reported error forms.