Update dependency @astrojs/mdx to v4 #42
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^3.1.7
->^4.0.0
Release Notes
withastro/astro (@astrojs/mdx)
v4.2.1
Patch Changes
#13448
91c9503
Thanks @ematipico! - Upgrade to shiki v3Updated dependencies [
91c9503
]:v4.2.0
Compare Source
Minor Changes
#13352
cb886dc
Thanks @delucis! - Adds support for a newexperimental.headingIdCompat
flagBy default, Astro removes a trailing
-
from the end of IDs it generates for headings ending withspecial characters. This differs from the behavior of common Markdown processors.
You can now disable this behavior with a new configuration flag:
This can be useful when heading IDs and anchor links need to behave consistently across your site
and other platforms such as GitHub and npm.
If you are using the
rehypeHeadingIds
plugin directly, you can also pass this new option:Patch Changes
cb886dc
,a3327ff
]:v4.1.1
Compare Source
Patch Changes
v4.1.0
Compare Source
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
1e11f5e
]:v4.0.8
Compare Source
Patch Changes
db252e0
]:v4.0.7
Compare Source
Patch Changes
cf30880
Thanks @ascorbic! - Upgrades Vitev4.0.6
Compare Source
Patch Changes
3d89e62
]:v4.0.5
Compare Source
Patch Changes
3a267f3
Thanks @bluwy! - Reverts withastro/astro@9a3b48c which caused a regression for rendering inline MDX components and MDX files from content collectionsv4.0.4
Compare Source
Patch Changes
#12921
aeb7e1a
Thanks @ascorbic! - Fixes a bug that caused Image component to be imported on MDX pages that did not include images#12913
9a3b48c
Thanks @bluwy! - Makes internalcheck()
function a no-op to allow faster component renders and prevent React 19 component warningsv4.0.3
Compare Source
Patch Changes
739dbfb
Thanks @ascorbic! - Upgrades Vite to pin esbuildv4.0.2
Compare Source
Patch Changes
f13417b
,87231b1
,a71e9b9
]:v4.0.1
Compare Source
Patch Changes
4f2fd0a
Thanks @Princesseuh! - Fixes compatibility with Astro 5v4.0.0
Compare Source
Major Changes
#12231
90ae100
Thanks @bluwy! - Handles the breaking change in Astro where content pages (including.mdx
pages located withinsrc/pages/
) no longer respond withcharset=utf-8
in theContent-Type
header.For MDX pages without layouts,
@astrojs/mdx
will automatically add the<meta charset="utf-8">
tag to the page by default. This reduces the boilerplate needed to write with non-ASCII characters. If your MDX pages have a layout, the layout component should include the<meta charset="utf-8">
tag.If you require
charset=utf-8
to render your page correctly, make sure that your layout components have the<meta charset="utf-8">
tag added.#12008
5608338
Thanks @Princesseuh! - Welcome to the Astro 5 beta! This release has no changes from the latest alpha of this package, but it does bring us one step closer to the final, stable release.Starting from this release, no breaking changes will be introduced unless absolutely necessary.
To learn how to upgrade, check out the Astro v5.0 upgrade guide in our beta docs site.
Minor Changes
#12539
827093e
Thanks @bluwy! - Drops node 21 support#11741
6617491
Thanks @bluwy! - Updates adapter server entrypoint to use@astrojs/mdx/server.js
This is an internal change. Handling JSX in your
.mdx
files has been moved from Astro internals and is now the responsibility of this integration. You should not notice a change in your project, and no update to your code is required.Patch Changes
#12075
a19530e
Thanks @bluwy! - Parses frontmatter ourselves#11861
3ab3b4e
Thanks @bluwy! - Updates@astrojs/markdown-remark
and handle its breaking changes#12533
1b61fdf
Thanks @ematipico! - Fixes a case where the MDX renderer couldn't be loaded when used as a direct dependency of an Astro integration.Updated dependencies [
3ab3b4e
,5608338
,560ef15
,83a2a64
,3ab3b4e
,a19530e
]:Configuration
📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.