-
-
Notifications
You must be signed in to change notification settings - Fork 356
Deprecate the Lazy Image package #2004
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
Comments
What is the "usual" scenario there?
This is very new to me ^^ |
I agree, my plan (whose timeline is unknown at this point), was to create a "recipe" system on ux.symfony.com first, then deprecate the ux components that could easily be replaced by a recipe (once the recipe exists). This allow us to point users to a concrete replacement. |
…ackage (javiereguiluz) This PR was merged into the 2.x branch. Discussion ---------- [Doc] Add a warning message to not recommend Lazy Image package | Q | A | ------------- | --- | Bug fix? | no | New feature? | no | Issues | | License | MIT Related to #2004. If we don't deprecate the package, at least warn users that it's no longer recommended. Thanks. Commits ------- 519c4ce [Doc] Add a warning message to not recommend Lazy Image package
Thank you for this issue. |
Friendly reminder that this issue exists. If I don't hear anything I'll close this. |
Hey, I didn't hear anything so I'm going to close it. Feel free to comment if this is still relevant, I can always reopen! |
As discussed in #1967, the solution proposed by the Lazy Image package (based on the "blurhash" library) was useful in the past. However, nowadays all browsers support many native features to improve the loading of images. See https://web.dev/learn/images/performance-issues
So, maybe we could deprecate this package to reduce the maintenance work? Thanks!
The text was updated successfully, but these errors were encountered: