5788f602a4
Use `WellKnownErrorsPlugin` when formatting `@next/font` errors. The error handling is different for expected errors (like validation errors) and unknown ones. If the error is expected it just displays the formatted error message. If it's an unknown error it will also display the stacktrace, and in case the versions of `@next/font` and `next` are different it will encourage you to try to update them both. Removes the usage of `error-loader` when importing from `pages/_document.js`, handle that case with `WellKnownErrorsPlugin` as well. The current warning when using different versions is removed. If the versions are incompatible you'll get an error in the overlay instead. ## 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)
3 lines
64 B
JavaScript
3 lines
64 B
JavaScript
export default function Index() {
|
|
return <p>Hello world</p>
|
|
}
|