-
Notifications
You must be signed in to change notification settings - Fork 26.2k
Provide image component similar to next/image #42765
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
Maybe relate to |
Yes or even For additional information: https://nextjs.org/docs/basic-features/image-optimization cheers |
There are multiple aspects to this feature, how it works also dependent on which image providers are used. This is because certain image providers (CDN) offer image optimisations out-of-box.
While the first can be archived using a purely client side component, The latter two would need to be handled during SSR. |
This feature request is now candidate for our backlog! In the next phase, the community has 60 days to upvote. If the request receives more than 20 upvotes, we'll move it to our consideration list. You can find more details about the feature request process in our documentation. |
I'd be happy to help in contributing this after a technical discussion |
@atscott Are here any updates? |
This would be a great feature to implement! |
We do have NgOptimizedImage directive starting from Angular 14.2 |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Feature Request
Relevant Package
Description
In Angular land, user has to first navigate to squoosh.app and shrink/resize the image before placing it under the
assets
folderDescribe the solution you'd like
Provide an angular component for image optimization similar to Next.js Image
Describe alternatives you've considered
Manually optimize JPG/PNG/WebP images using squoosh.app and SVG using SVGOMG
The text was updated successfully, but these errors were encountered: