Skip to content

Docs: unfreeze five React pages stuck on live since 22 September - #594

Open
amitthacker-maker wants to merge 1 commit into
cometchat:mainfrom
amitthacker-maker:fix/react-peer-dep-range-mdx-parse
Open

amitthacker-maker wants to merge 1 commit into
cometchat:mainfrom
amitthacker-maker:fix/react-peer-dep-range-mdx-parse

Conversation

@amitthacker-maker

Copy link
Copy Markdown

Five React pages have been serving pre-22-September content on live for six weeks. The cause is four missing backtick characters per line.

Found by @raj-dubey1 while reviewing #585. This is not a #585 problem, it is already on main, and it should merge before #585.

The bug

The version range sat outside its code span:

| Peer deps | `react` >=18 <21, `react-dom` >=18 <21, ... |

<21, is bare MDX, so it parses as a JSX tag open. Affected, all at line 12 on main:

  • ui-kit/react/overview.mdx
  • ui-kit/react/integration-react.mdx
  • ui-kit/react/integration-nextjs.mdx
  • ui-kit/react/integration-astro.mdx
  • ui-kit/react/integration-react-router.mdx

Why it went unnoticed

All five return HTTP 200 on live. They serve the last build that succeeded, so nothing looks broken from the outside and neither the Mintlify Deployment check nor link-rot catches it.

The cause is isolated, not inferred

On the #585 preview, a real Mintlify build, the five pages 308-redirect to Home while controls return 200:

Page Preview
the five above 308 to /
ui-kit/react/components/conversations 200
ui-kit/react/migration-overview 200
fundamentals/pin-message 200

migration-overview is the control that settles it. It carries the same >=18 <21 text at line 53, but inside backticks, and it builds and serves normally. Same text, same page family, only the code span differs.

What live is serving

Live main
4.1.9 occurrences 3, 2, 2, 2, 2 0
4.2.0 occurrences 0 3, 1, 1, 1, 1
dompurify listed as a peer dependency bundled

Live tells a React developer the SDK peer dependency is ^4, which permits 4.0.x. The real floor for UI Kit 7.2.x is 4.2.0, so following the published page produces a broken install. The per-release floors (7.0.3 needs 4.1.12, 7.1.0 needs 4.1.13, 7.2.x needs 4.2.0) were written on 22 September and have never reached a reader.

The served .md output carries the same stale table, so coding agents and answer engines are being given the wrong dependency facts too.

Scope

Exactly five lines. A repo-wide grep for < followed by a digit in .mdx returns 10 hits; the other five are safe inside backticks or a ```swift fence (calls/flutter/overview.mdx:18, `ui-kit/react-native/upgrading-from-v4.mdx:646`, `ui-kit/react-native/property-changes.mdx:438`, `ui-kit/react/migration-overview.mdx:12,53`, `sdk/ios/3.0/send-a-message.mdx:426`).

Also unblocks

Three commits of corrections have been stuck behind this: v7 API errors and SSR guidance (3f8bc8c), and overlay containment (8cd8e5a, 4dcfda3).

Worth checking after merge

Live is probably still serving only because of a cached last-good build. Please confirm the five pages render current content once this deploys, rather than redirecting to Home.

Introduced by 412df50, merged via #518.

🤖 Generated with Claude Code

Five React pages have been serving pre-22-September content on live since
412df50, and the cause is four missing backticks per line.

The version range sat outside the code span:

    `react` >=18 <21

so `<21,` is bare MDX and parses as a JSX tag open. The five pages still
return 200 on live, which is why no check caught it, but they render the
state of the file before the break. Live tells a React developer the SDK
peer dependency is `^4`, which permits 4.0.x; the real floor for UI Kit
7.2.x is 4.2.0, so following the published page produces a broken install.

The same text already appears correctly elsewhere, inside backticks, on
ui-kit/react/overview.mdx:97-98 and ui-kit/react/migration-overview.mdx:53.
migration-overview builds and serves normally, which is what isolates the
cause to the code span rather than to the text.

This also unblocks three commits of corrections that have been stuck behind
the break: v7 API errors and SSR guidance (3f8bc8c) and overlay containment
(8cd8e5a, 4dcfda3).

Found by raj-dubey1 in review of cometchat#585.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@mintlify

mintlify Bot commented Nov 2, 2026

Copy link
Copy Markdown

Preview approval required

This pull request comes from a fork, so Mintlify won't build a preview until someone with write access approves commit 7fe932f.

Approve preview

@amitthacker-maker

Copy link
Copy Markdown
Author

This can be closed. Main already carries the fix, reached a different way.

The problem was that >=18 <21 sat outside a code span, so <21 was read as the start of a tag and the parse failed. This branch solved it by pulling the whole dependency and its range into one span: `react >=18 <21`.

Main now writes it as two spans instead, the name and then the range: `react` `>=18 <21`. Checked on all five files this branch touches, and all five read that way on main today. The parse hazard is gone either way.

No objection to the branch, it is just no longer needed, and it conflicts because both sides edited the same line.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants