-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Improve markdown rendering performance #8532
Conversation
🦋 Changeset detectedLatest commit: 93f7b53 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
const astroData = safelyGetAstroData(renderResult.vfile.data); | ||
if (astroData instanceof InvalidAstroDataError) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
astroData
here is used for astroData.frontmatter
only. I moved frontmatter
to return directly from processor.render()
above instead.
const astroData = safelyGetAstroData(result.data); | ||
if (astroData instanceof InvalidAstroDataError) { | ||
throw astroData; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rendering markdown now handles and throws InvalidAstroDataError
directly. Otherwise the consumer who have needed to do it manually.
Changes
Improve markdown rendering performance by sharing the markdown/unified processor.
Will be doing the same for MDX next.
I tried benchmarking this, but unfortunately they don't show a big difference. Technically it should improve things though. When I finish the MDX change I could probably test it on our docs build and see if there's a clearer difference there.
Testing
Ran astro/remark/mdx tests locally.
Docs
n/a