Repository navigation
refactor(v2): use forked lqip-loader for performance - #1680
Merged
Merged
Conversation
Contributor
|
Deploy preview for docusaurus-2 ready! Built with commit fa9c0c8 |
Contributor
|
Deploy preview for docusaurus-preview ready! Built with commit fa9c0c8 |
mrizwanashiq
pushed a commit
to mrizwanashiq/docusaurus
that referenced
this pull request
Jun 25, 2026
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
3 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.
Motivation
I forked https://github.com/zouhir/lqip-loader to https://github.com/endiliey/lqip-loader because the original version uses jimp, which is an image processing library that is so much slower than sharp
Check this benchmark for jimp vs sharp
https://sharp.pixelplumbing.com/en/stable/performance/
Have you read the Contributing Guidelines on pull requests?
yes
Test Plan
before
after
before in prod
after in prod
