Fix MDX parsing error in CLI changelog #2065
Open
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
Wrap {API name} and X/Y in inline code to prevent MDX parser from treating curly braces as JSX expressions, which was causing 'Could not parse expression with acorn' error during docs generation.
Co-Authored-By: Chris McDonnell <[email protected]>
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Contributor
devin-ai-integration bot
added a commit
that referenced
this pull request
Nov 18, 2025
Wrap {API name} and X/Y placeholders in backticks to prevent MDX parser
from treating curly braces as JSX expressions. This fixes the 'Could not
parse expression with acorn' error that was blocking CI.
This fix is bundled with the Fern Editor component updates to unblock CI
on this PR. The same fix was proposed in PR #2065 but hasn't been merged yet.
Co-Authored-By: Chris McDonnell <[email protected]>
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix MDX parsing error in CLI changelog (2025-11-14)
Summary
Fixes an MDX parsing error in the CLI changelog that was causing
fern generate --docs --previewto fail with "Could not parse expression with acorn". The issue was introduced in PR #2063 when the 2025-11-14.mdx changelog was added.The problem: MDX treats curly braces
{...}as JSX expressions. The text{API name}andX/Yin the changelog entry were being interpreted as code rather than literal text, causing a parse error.The fix: Wrapped both placeholders in inline code backticks (
`{API name}`and`X/Y`), which is the standard MDX approach for escaping special characters and is semantically appropriate since these are literal placeholders.Review & Testing Checklist for Human
/learn/cli-api-reference/cli-changelogrenders correctly with the inline code stylingNotes
{API name}andX/Yare placeholders/literals