You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Provide image component similar to next/image #42765
Yes or even @angular/cli because the optimization of next/image happens on server side with a node instance that serves the next app. It's not just a react component, there is more behind it.
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.
When using one of the supported image providers, queries are added to the request, this is done so that the image is resized and optimised directly the provider.
When the image is remotely stored but the provider is not supported during request time the image is downloaded, optimized, cached and served.
When the image from the local FS, similar to remote images, during request time the image is read, optimised, cached and served.
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.
Activity
splincode commentedon Jul 5, 2021
Maybe relate to
@angular/cdk/image?flash-me commentedon Jul 5, 2021
Yes or even
@angular/clibecause the optimization ofnext/imagehappens on server side with a node instance that serves the next app. It's not just a react component, there is more behind it.For additional information: https://nextjs.org/docs/basic-features/image-optimization
cheers
flash ⚡
alan-agius4 commentedon Jul 5, 2021
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.
angular-robot commentedon Jul 5, 2021
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.
samuelfernandez commentedon Jul 6, 2021
I'd be happy to help in contributing this after a technical discussion
conradkirschner commentedon Mar 10, 2022
@atscott Are here any updates?
HamzaMoiyadi commentedon Apr 5, 2022
This would be a great feature to implement!
Any updates? Would love to contribute as well
otodockal commentedon Apr 5, 2022
@HamzaMoiyadi @conradkirschner https://angular.io/guide/roadmap#improve-image-performance
[-]Provide @angular/image component similar to next/image[/-][+]Provide image component similar to next/image[/+]pkozlowski-opensource commentedon Jan 11, 2023
We do have NgOptimizedImage directive starting from Angular 14.2
angular-automatic-lock-bot commentedon Feb 11, 2023
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.