[docs-infra] Add comment about removing optimizeFonts Next.js config #43469
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aarongarciah
added
the
internal
aarongarciah
added
nextjs
scope: docs-infra
Netlify deploy previewhttps://deploy-preview-43469--material-ui.netlify.app/ Bundle size report |
aarongarciah
changed the title
alexfauquette
approved these changes
Aug 27, 2024
This was referenced Sep 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Next.js v15 drops support for the
optimizeFontsoption (see vercel/next.js#69137) and warns about this option being invalid. I'm adding a comment so we don't forget about it.Next.js v15 build time warning: