Improve error handling for packages that don't run on the edge

[mintydev789]

Goals

1. Greatly improve the developer experience, when it comes to debugging.
2. Clarify how to fix issues with those types of packages.

Non-Goals

1. It does not aim to magically make those packages run on the edge.
2. It does not aim to change anything in the docs, just improve error handling.

Background

This feature is really needed, because right now, if you use one of those packages without realizing it's not supported by edge runtimes, you'll get a very cryptic and unhelpful error message. For example, when I was working with the Pino library, I kept getting an error related to a file not being found, because Pino uses worker threads, which only work with Node. There is currently no intuitive way to figure out that this is caused by the lack of edge runtime support in the package.

Proposal

Implenent a way to detect when the code uses features not supported on the edge, and display an error that instructs the developer that they may be using an unsupported feature (e.g. worker threads, like in my example) and that if it's used in a package, that package must be added to the external packages array in the Next JS config file.

[icyJoseph]

Btw, if you are in latest Next.js, the nodejs runtime is available for middleware. Proxy defaults to nodejs and it is not configurable.

[mintydev789]

Maybe that could also be one of the options in the error message: that the runtime can be changed to nodejs.