Skip to content

Ensure maximum compatibility with mdx-bundler#19

Merged
timlrx merged 2 commits into
timlrx:mainfrom
eps1lon:mdx-bundler-compat
May 30, 2024
Merged

Ensure maximum compatibility with mdx-bundler#19
timlrx merged 2 commits into
timlrx:mainfrom
eps1lon:mdx-bundler-compat

Conversation

@eps1lon

@eps1lon eps1lon commented May 28, 2024

Copy link
Copy Markdown
Contributor

mdx-bundler doesn't document usage without its client entrypoint. This replaces the custom implementation of getMDXComponent with the one exported by mdx-bundler/client. Otherwise changes such as kentcdodds/mdx-bundler#229 would break next-contentlayer.

We're using this patch at Vercel in nextjs.org already.

eps1lon added 2 commits May 28, 2024 16:27
mdx-bundler doesn't document usage without its client entrypoint.
This replaces the custom implementation of `getMDXComponent` with the one exported by `mdx-bundler/client`.

We're using this patch at Vercel in nextjs.org already.
@eps1lon eps1lon force-pushed the mdx-bundler-compat branch from 6df8467 to ab5b962 Compare May 28, 2024 15:37
@eps1lon eps1lon marked this pull request as ready for review May 28, 2024 17:30
@eps1lon

eps1lon commented May 29, 2024

Copy link
Copy Markdown
Contributor Author

How reliable are these Windows runs? Can't see any change that would only break on Windows but pass on Linux and macOS.

@timlrx

timlrx commented May 30, 2024

Copy link
Copy Markdown
Owner

How reliable are these Windows runs? Can't see any change that would only break on Windows but pass on Linux and macOS.

It's an existing issue with Contentlayer and unrelated to this PR. The fix looks good to me, thanks!

@timlrx timlrx merged commit e6b9bd0 into timlrx:main May 30, 2024
@eps1lon eps1lon deleted the mdx-bundler-compat branch May 30, 2024 15:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants