Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure maximum compatibility with mdx-bundler #19

Merged
merged 2 commits into from
May 30, 2024

Conversation

eps1lon
Copy link
Contributor

@eps1lon eps1lon commented May 28, 2024

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.

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 marked this pull request as ready for review May 28, 2024 17:30
@eps1lon
Copy link
Contributor Author

eps1lon commented May 29, 2024

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

@timlrx
Copy link
Owner

timlrx commented May 30, 2024

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
51 of 56 checks passed
@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