-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Investigate & upgrade next-mdx-remote
to v4
#11938
Comments
next-mdx-remote
next-mdx-remote
to v4
@pettinarip took time to check this out. Did a bump to
<DocLink>
{ "Ethereum security and scam prevention" }
</DocLink>
I am not seeing anything else to address at that version to prevent breaking. Anything different you have in mind here? |
This issue is stale because it has been open 45 days with no activity. |
@pettinarip commenting for assignment, per private discussion, and I will attempt to use my suggestion above to see what effect it has at this point. |
@TylerAPfledderer assigned, thanks! |
This issue is stale because it has been open 45 days with no activity. |
Closing via this comment: #12055 (comment) |
Important: we can't upgrade to v4 with the current code as it is. See ethereum#18 for more details about why we downgraded to v3.
Investigate how to fix the issues we have with
next-mdx-remote
v4 and upgrade it https://github.com/hashicorp/next-mdx-remoteWe could potentially replace
gray-matter
since the new version can parse frontmatter as well and simplify a bit the code.The text was updated successfully, but these errors were encountered: