Hannes Bornö b3f3bf59b9 Improve app-render error log with edge runtime (#46157) ... `app-render` server errors aren't logged correctly with the edge runtime. This adds logging of a filtered stack trace. Before  After  Still some improvements left to figure out. This change doesn't log the original stack frame, and the `Log.error` is not printed with a red text like it should be. Fixes NEXT-593 ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md) ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] [e2e](https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md) ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm build && pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)		2023-02-20 16:24:15 +00:00
..
app	Improve app-render error log with edge runtime (#46157)	2023-02-20 16:24:15 +00:00
app-render-error-log.test.ts	Improve app-render error log with edge runtime (#46157)	2023-02-20 16:24:15 +00:00
next.config.js	Make app-render error logging less verbose in dev (#45472)	2023-02-14 18:46:30 -08:00