fix: move katex CSS import from client component to root layout - #301
Open
Hanhai Zou (zouhanhai) wants to merge 1 commit into
Open
fix: move katex CSS import from client component to root layout#301Hanhai Zou (zouhanhai) wants to merge 1 commit into
Hanhai Zou (zouhanhai) wants to merge 1 commit into
Conversation
…ex.min.css from a client component\n(markdown-text.tsx) causes Next.js flight-css-loader to fail with:\n"Module parse failed: Unexpected character '@'"\n\nMoving the import to layout.tsx (server component) allows Next.js\nto process the CSS correctly via the regular CSS pipeline.
|
Hanhai Zou (@zouhanhai) is attempting to deploy a commit to the LangChain Team on Vercel. A member of the Team first needs to authorize it. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Problem
import "katex/dist/katex.min.css"frommarkdown-text.tsx(client component) causes Next.js 15.5+ to fail with:Both
next devandnext startreturn 500.Fix
Move CSS import from client component to root layout (server component). Next.js processes CSS correctly in server components via the regular CSS pipeline.
Verification
next build→ passes