Releases: withastro/astro
@astrojs/[email protected]
Minor Changes
-
#13254
1e11f5e
Thanks @p0lyw0lf! - Adds the ability to process and optimize remote images in Markdown syntax in MDX files.Previously, Astro only allowed local images to be optimized when included using
![]()
syntax. Astro's image service could only display remote images without any processing.Now, Astro's image service can also optimize remote images written in standard Markdown syntax. This allows you to enjoy the benefits of Astro's image processing when your images are stored externally, for example in a CMS or digital asset manager.
No additional configuration is required to use this feature! Any existing remote images written in Markdown will now automatically be optimized. To opt-out of this processing, write your images in Markdown using the JSX
<img/>
tag instead. Note that images located in yourpublic/
folder are still never processed.
Patch Changes
- Updated dependencies [
1e11f5e
]:- @astrojs/[email protected]
@astrojs/[email protected]
Minor Changes
-
#13254
1e11f5e
Thanks @p0lyw0lf! - Adds remote image optimization in MarkdownPreviously, an internal remark plugin only looked for images in
![]()
syntax that referred to a relative file path. This meant that only local images stored insrc/
were passed through to an internal rehype plugin that would transform them for later processing by Astro's image service.Now, the plugins recognize and transform both local and remote images using this syntax. Only authorized remote images specified in your config are transformed; remote images from other sources will not be processed.
While not configurable at this time, this process outputs two separate metadata fields (
localImagePaths
andremoteImagePaths
) which allow for the possibility of controlling the behavior of each type of image separately in the future.
Patch Changes
- Updated dependencies [
1e11f5e
]:- @astrojs/[email protected]
@astrojs/[email protected]
Patch Changes
-
#13323
80926fa
Thanks @ematipico! - Updatesesbuild
andvite
to the latest to avoid false positives audits warnings caused byesbuild
. -
Updated dependencies [
1e11f5e
,1e11f5e
]:- @astrojs/[email protected]
- @astrojs/[email protected]
@astrojs/[email protected]
@astrojs/[email protected]
Patch Changes
-
#13314
797a948
Thanks @jlebras! - Exposeilike
function fromdrizzle-orm
-
Updated dependencies []:
- @astrojs/[email protected]
@astrojs/[email protected]
Patch Changes
-
#13323
80926fa
Thanks @ematipico! - Updatesesbuild
andvite
to the latest to avoid false positives audits warnings caused byesbuild
. -
Updated dependencies [
1e11f5e
]:- @astrojs/[email protected]
- @astrojs/[email protected]
[email protected]
[email protected]
Patch Changes
-
#13233
32fafeb
Thanks @joshmkennedy! - Ensures consistent behaviour ofAstro.rewrite
/ctx.rewrite
when usingbase
andtrailingSlash
options. -
#13003
ea79054
Thanks @chaegumi! - Fixes a bug that caused thevite.base
value to be ignored when runningastro dev
-
#13299
2e1321e
Thanks @bluwy! - Usestinyglobby
for globbing files -
#13233
32fafeb
Thanks @joshmkennedy! - Ensures thatAstro.url
/ctx.url
is correctly updated with thebase
path after rewrites.This change fixes an issue where
Astro.url
/ctx.url
did not include the configured base path after Astro.rewrite was called. Now, the base path is correctly reflected in Astro.url.Previously, any rewrites performed through
Astro.rewrite
/ctx.rewrite
failed to append the base path toAstro.url
/ctx.rewrite
, which could lead to incorrect URL handling in downstream logic. By fixing this, we ensure that all routes remain consistent and predictable after a rewrite.If you were relying on the work around of including the base path in astro.rewrite you can now remove it from the path.
@astrojs/[email protected]
Patch Changes
- #13251
3842ce5
Thanks @florian-lefebvre! - Fixes a case where the compiler could not be resolved automatically