584d842ae0
Similar to https://github.com/vercel/next.js/pull/42106. Make `@next/font` works as expected when using `transpilePackages`. Also makes sure `@next/font` is auto-configured correctly when in a monorepo. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `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` - [ ] Integration 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` ## 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) Co-authored-by: JJ Kasper <jj@jjsweb.site>
14 lines
534 B
Markdown
14 lines
534 B
Markdown
# Babel and `@next/font` conflict
|
|
|
|
#### Why This Error Occurred
|
|
|
|
You have tried to use `@next/font` with a custom babel config. When your application has a custom babel config you opt-out of the Next.js Compiler which is required to use `@next/font`.
|
|
|
|
#### Possible Ways to Fix It
|
|
|
|
- Remove your custom babel config and use the Next.js Compiler
|
|
|
|
### Useful Links
|
|
|
|
- [Next.js Compiler](https://nextjs.org/docs/advanced-features/compiler)
|
|
- [Customizing Babel Config](https://nextjs.org/docs/advanced-features/customizing-babel-config)
|