a548223 Thanks @matthewp! - Fixes <script>/<style> rendering in MDX so that only literal content (including content injected by remark/rehype plugins) is treated as trusted markup. A dynamic value passed as a <script>/<style> child (e.g. <script>{value}</script>) is now escaped like any other element’s content instead of being rendered raw. Use set:html to explicitly opt a dynamic value back into raw rendering.#17262 f8e9458 Thanks @Princesseuh! - Adds MDX rendering to the unified() and satteri() processors.
Both processors now compile .mdx files themselves. You still need to install @astrojs/mdx to add MDX support to your project.
#17262 f8e9458 Thanks @Princesseuh! - Adds a recmaPlugins option to unified() for adding recma (estree/JSX) plugins to the MDX compiler.
f8e9458]:
05763a0]:
8c193f6]:
c895b12]:
eb6f97e]:
#16848 f732f3c Thanks @Princesseuh! - Adds a new markdown.processor configuration option, allowing you to choose an alternative Markdown processor.
Websites with many Markdown/MDX files tend to be slow to build because the unified ecosystem (e.g., remark, rehype) is slow to process. This feature introduces the ability to replace this part of the build pipeline with another processor.
The default processor is unified(). This means that existing configurations remain unchanged and your remark/rehype plugins continue to work.
import { defineConfig } from 'astro/config';import { unified } from '@astrojs/markdown-remark';import remarkToc from 'remark-toc';
export default defineConfig({ markdown: { processor: unified({ remarkPlugins: [remarkToc], }), },});In addition to this new configuration option, Astro provides a new alternative processor based on Rust: Sätteri. You can choose to use it now by installing @astrojs/markdown-satteri, importing the satteri() processor, and adapting your existing configuration:
import { defineConfig } from 'astro/config';import { satteri } from '@astrojs/markdown-satteri';
export default defineConfig({ markdown: { processor: satteri({ features: { directive: true }, }), },});This processor does not support the remark and rehype plugins. This means you may need to convert them to MDAST or HAST plugins to retain your current functionality.
The existing top-level markdown.remarkPlugins, markdown.rehypePlugins, markdown.remarkRehype, markdown.gfm, and markdown.smartypants options still work, but are now deprecated and will be removed in a future major update. The matching remarkPlugins, rehypePlugins, and remarkRehype options on the MDX integration are also deprecated for the same reason. To anticipate their removal, move them onto unified({...}) (or your preferred plugin processor) :
import { defineConfig } from 'astro/config';import remarkToc from 'remark-toc';import rehypeSlug from 'rehype-slug'; import { unified } from '@astrojs/markdown-remark';
export default defineConfig({ markdown: { processor: unified({ remarkPlugins: [remarkToc], rehypePlugins: [rehypeSlug], remarkRehype: true, gfm: true, smartypants: true, }), remarkPlugins: [remarkToc], rehypePlugins: [rehypeSlug], remarkRehype: true, gfm: true, smartypants: true, },});For more information on enabling and using this feature in your project, see our Markdown guide. To give feedback on this new Rust processor, see the Native Markdown / MDX parsing and processing RFC.
f732f3c]:
#15340 10a1a5a Thanks @trueberryless! - Updates createMarkdownProcessor to support advanced SmartyPants options.
The smartypants property in AstroMarkdownOptions now accepts Smartypants options, allowing fine-grained control over typography transformations (backticks, dashes, ellipses, and quotes).
import { createMarkdownProcessor } from '@astrojs/markdown-remark';
const processor = await createMarkdownProcessor({ smartypants: { backticks: 'all', dashes: 'oldschool', ellipses: 'unspaced', openingQuotes: { double: '«', single: '‹' }, closingQuotes: { double: '»', single: '›' }, quotes: false, },});For the up-to-date supported properties, check out the retext-smartypants options.
d3c7de9]:
c2cd371]:
#14494 727b0a2 Thanks @florian-lefebvre! - Updates Markdown heading ID generation - (v6 upgrade guidance)
#15726 6f19ecc Thanks @ocavue! - Updates dependency shiki to v4
Check Shiki’s upgrade guide.
#15277 cb99214 Thanks @ematipico! - Fixes an issue where the function createShikiHighlighter would always create a new Shiki highlighter instance. Now the function returns a cached version of the highlighter based on the Shiki options. This should improve the performance for sites that heavily rely on Shiki and code in their pages.
#15332 7c55f80 Thanks @matthewp! - Exposes the fileURL option in MarkdownProcessorRenderOptions, allowing callers to specify the file URL for resolving relative image paths.
#15297 80f0225 Thanks @rururux! - Fixes a case where code blocks generated by prism would include the is:raw attribute in the final output
#15676 1fa4177 Thanks @rururux! - Fixes an issue where the use of the Code component would result in an unexpected error.
#15651 f94d3c5 Thanks @ocavue! - Reuses cached Shiki highlighter instances across languages.
Updated dependencies [bbb5811, 4ebc1e3, 11efb05, 4e7f3e8, a164c77, cf6ea6b, e131261, a18d727, 240c317, 745e632]:
745e632]:
84d6efd Thanks @ematipico! - Changes how styles applied to code blocks are emitted to support CSP - (v6 upgrade guidance)