Use different font in development in next webpack config #13035
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
FinnIckler
reviewed
Dec 16, 2025
| webpack(config) { | ||
| if (!process.env.PROPRIETARY_FONT) { | ||
| config.resolve.alias["@/styles/fonts"] = | ||
| require("path").resolve(__dirname, "src/styles/fonts/empty-font.ts"); |
Member
There was a problem hiding this comment.
I assume this is not possible to do via import?
Contributor
Author
There was a problem hiding this comment.
Are you referring specifically to require("path"). I hadn't thought of it, yeah should be able to change to import I think.
Member
There was a problem hiding this comment.
yes, please use the import then. We should only be using require if it's needed for a commonjs module as per @typescript-eslint/no-require-imports
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Summary
Fix issue with prod fonts trying to be loaded in development.
This issue is fixed by loading a different font via the nextjs webpack config.