-
Notifications
You must be signed in to change notification settings - Fork 3
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
perf(mdx): optimize mdx related components render performance #827
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Lighthouse Report✨ https://blog-ay71o0og2-sabertaz.vercel.app/🚀 Vercel preview deployment
✨ https://blog-ay71o0og2-sabertaz.vercel.app/posts🚀 Vercel preview deployment
✨ https://blog-ay71o0og2-sabertaz.vercel.app/tags🚀 Vercel preview deployment
✨ https://blog-ay71o0og2-sabertaz.vercel.app/books🚀 Vercel preview deployment
✨ https://blog-ay71o0og2-sabertaz.vercel.app/about🚀 Vercel preview deployment
|
Codecov Report
@@ Coverage Diff @@
## main #827 +/- ##
==========================================
- Coverage 99.40% 99.40% -0.01%
==========================================
Files 175 175
Lines 1001 1000 -1
Branches 83 83
==========================================
- Hits 995 994 -1
Misses 5 5
Partials 1 1
Continue to review full report at Codecov.
|
This PR has Quantification details
Why proper sizing of changes matters
Optimal pull request sizes drive a better predictable PR flow as they strike a
What can I do to optimize my changes
How to interpret the change counts in git diff output
Was this comment helpful? 👍 :ok_hand: :thumbsdown: (Email) |
close #826
Pull Request
This PR Contains
Motivation / Use-Case
Breaking Changes
Test-Case
I have verified these changes via:
Additional Info