Avoid Astro 6.4 deprecation warnings#449
Merged
delucis merged 1 commit intoJun 9, 2026
Merged
Conversation
✅ Deploy Preview for expressive-code ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
delucis
approved these changes
Jun 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 refactors how the Astro Expressive Code integration registers its Markdown plugin.
processor.options.rehypePlugins. This avoids a deprecation warning:[astro] 'markdown.remarkPlugins', 'markdown.rehypePlugins', and 'markdown.remarkRehype' are deprecated. Pass them to 'unified({...})' from '@astrojs/markdown-remark' directly instead.<Code>component.For tests, I renamed the existing 6.4 fixture to "astro-6.4.0-satteri" and made a new "astro-6.4.0-unified" fixture. This seemed more in line with the current testing strategy in the project but I'm not familiar with it so let me know if you'd prefer a different approach.