-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add proper image processing (resizing/optimisation) into Astro build process #58
Comments
Astro itself launched an Image component. See https://github.com/withastro/astro/tree/main/packages/integrations/image We will wait until Astro is either 1.0.0 stable or this component have been moved out of the experimental status. Until then: This ticket is on-hold |
I ran into this. The experience is not fun. *.mdx integration handles the optimized assets correctly without any kind of special component. But, you cannot glob *.mdx the same way - the .file property is empty, breaking all my *.md globs. I tried the experimental component and it did not work. If this already works for *.mdx, why not port the changes to regular Markdown? |
And it also does not support something for scss or sass so we can use image-set for background and stuff. That would also be very useful. |
It would be ideal to have support for this resizing/optimization to also happen for images imported into react/vue/etc components at least as long as the component itself is static. |
FYI:
We will wait until Astro v3 is out and then directly use the new asset module. |
…te (to generate it to webp) Related #58
Primarily done. |
Most of the pictures are either not optimized or simple way too big.
It would make sense to add an additional step into the build process to optimize the pictures.
Resources:
The text was updated successfully, but these errors were encountered: