Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
mapachurro
approved these changes
Mar 11, 2025
Contributor
mapachurro
left a comment
mapachurro
left a comment
There was a problem hiding this comment.
I honestly do not understand the React.ReactNode thing. If you're uncomfortable with it, I'm happy to dig in tomorrow -- but for the time being, it builds fine in local for me, and is passing tests, so 👍
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumping Docusaurus to 3.7.0, and also trying to address a security vulnerability (on
prismjsthat affects versions older than 1.30.0.Subsequently ended up updating some swizzled components, since Docusaurus 3.7.0 added a change that replaced some
JSX.Elementusage withReact.ReactNode: facebook/docusaurus#10747