Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion apps/dev-portal-web/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@
"gray-matter": "4.0.3",
"lodash": "^4.17.21",
"next": "^15.5.9",
"next-mdx-remote": "4.3.0",
"next-mdx-remote": "6.0.0",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Preserve MDX JS expressions when upgrading to v6

next-mdx-remote 6.0.0 changes JS handling defaults (blockJS/blockDangerousJS default to true), but extractMdx still calls serialize() without overriding those flags, while existing docs rely on MDX JS expressions (for example component props like labels={['npm', 'yarn', 'pnpm']} in apps/dev-portal-web/docs/ui/about.en.mdx). This can break server-side compilation/rendering of documentation pages after the dependency bump unless the serializer options are updated or docs are migrated away from JS expressions.

Useful? React with 👍 / 👎.

"next-seo": "^6.4.0",
"phone": "^3.1.41",
"react": "^18.3.1",
Expand Down
Loading
Loading