fix: bump fumadocs-core to fix breaking build - #186
Merged
Merged
Conversation
…e stack mdast-util-to-markdown 2.1.3 serialises strong and emphasis through containerPhrasing, which reads an `attention` property off the handler. fumadocs-core's stringifier wraps every handler in a new function and, before 16.15.15, dropped that property. The strong handler then calls containerPhrasing, which calls the wrapped strong handler again, until the build fails with "Maximum call stack size exceeded" on any page with bold or italic text. fumadocs-core pins mdast-util-to-markdown with a caret, so every fresh install of chronicle picks up 2.1.3 and breaks. 16.15.15 copies the handler's properties onto the wrapper. The lockfile moves mdast-util-to-markdown to 2.1.3 as well, so CI builds against the version a fresh install resolves.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Repository: raystack/chronicle/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
rohanchkrabrty
changed the title
rohanchkrabrty
requested review from
rsbh
and removed request for
Shreyag02
September 28, 2026 17:01
rsbh
approved these changes
Sep 28, 2026
This branch was successfully deployed
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
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
fumadocs-corefrom 16.15.4 to 16.15.15. Any page with bold or italic text currently fails to build withMaximum call stack size exceeded.mdast-util-to-markdown2.1.3 (released 2026-09-27) formatsstrong/emphasisthroughcontainerPhrasing, which reads anattentionproperty on the handler. Before 16.15.15, fumadocs-core's stringifier wrapped each handler without copying its properties, sostrongandcontainerPhrasingcalled each other forever.fumadocs-coreacceptsmdast-util-to-markdown^2.1.2, so every fresh install (e.g.bunx @raystack/chronicle build) picks up 2.1.3 and breaks. Chronicle's CI didn't catch it because the lockfile was still on 2.1.2.mdast-util-to-markdownto 2.1.3 too, so CI builds against the version a fresh install gets.