-
Notifications
You must be signed in to change notification settings - Fork 201
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
Support Remix #169
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Nearly 100 people have requested this feature—I'd suggest we not close this without making an active decision that it shouldn't be prioritized. |
Is there anything happening on this front? |
We haven't started this work. The first task is to assess the work needed to properly hook into the Remix development and build/production processes. For those interested in this support, will someone share a proof of concept of manually starting the contentlayer In addition, is there any behavior in Remix worth noting or looking out for? This should help assess what it will take to develop a more seamless plugin. |
What's the alternative to contentlayer for making Mdx work with Remix? Migrating from Next.js to Remix |
I don't have much experience with Remix. However, Contentlayer should work with Remix. The lack of a direct integration really just means that it's not automatically wired into the development server. You'd have to run the Contentlayer dev process alongside the remix development server. That said, here's some information about handling MDX with Remix in case you want to work with a different solution. |
mdx-bundler is helpful. |
Add your vote for Remix support by clicking the 👍 emoji below.
The text was updated successfully, but these errors were encountered: