#5825 52209ca2a Thanks @bholmesdev! - Baseline the experimental contentCollections flag. You’re free to remove this from your astro config!
import { defineConfig } from 'astro/config';
export default defineConfig({ experimental: { contentCollections: true }})1f92d64ea Thanks @Princesseuh! - Remove support for Node 14. Minimum supported Node version is now >=16.12.0#5769 93e633922 Thanks @bholmesdev! - Introduce a smartypants flag to opt-out of Astro’s default SmartyPants plugin.
{ markdown: { smartypants: false, }}You may have disabled Astro’s built-in plugins (GitHub-Flavored Markdown and Smartypants) with the extendDefaultPlugins option. This has now been split into 2 flags to disable each plugin individually:
markdown.gfm to disable GitHub-Flavored Markdownmarkdown.smartypants to disable SmartyPantsimport { defineConfig } from 'astro/config';
export default defineConfig({ markdown: { extendDefaultPlugins: false, smartypants: false, gfm: false, }});#5687 e2019be6f Thanks @bholmesdev! - Give remark and rehype plugins access to user frontmatter via frontmatter injection. This means data.astro.frontmatter is now the complete Markdown or MDX document’s frontmatter, rather than an empty object.
This allows plugin authors to modify existing frontmatter, or compute new properties based on other properties. For example, say you want to compute a full image URL based on an imageSrc slug in your document frontmatter:
export function remarkInjectSocialImagePlugin() { return function (tree, file) { const { frontmatter } = file.data.astro; frontmatter.socialImageSrc = new URL(frontmatter.imageSrc, 'https://my-blog.com/').pathname; };}remarkPluginFrontmatter propertyWe have changed inject frontmatter to modify frontmatter in our docs to improve discoverability. This is based on support forum feedback, where “injection” is rarely the term used.
To reflect this, the injectedFrontmatter property has been renamed to remarkPluginFrontmatter. This should clarify this plugin is still separate from the data export Content Collections expose today.
Plugin authors should now check for user frontmatter when applying defaults.
For example, say a remark plugin wants to apply a default title if none is present. Add a conditional to check if the property is present, and update if none exists:
export function remarkInjectTitlePlugin() { return function (tree, file) { const { frontmatter } = file.data.astro; if (!frontmatter.title) { frontmatter.title = 'Default title'; } }}This differs from previous behavior, where a Markdown file’s frontmatter would always override frontmatter injected via remark or reype.
#5684 a9c292026 Thanks @bholmesdev! - Refine Markdown and MDX configuration options for ease-of-use.
remark-smartypants from Astro’s default Markdown plugins.extendDefaultPlugins option with a simplified gfm boolean. This is enabled by default, and can be disabled to remove GitHub-Flavored Markdown.remarkPlugins or rehypePlugins are configured. If you want to apply custom plugins and remove GFM, manually set gfm: false in your config.drafts) from your MDX integration config. This includes syntaxHighlighting and shikiConfig options to further customize the MDX renderer.extendDefaults to an extendMarkdownConfig option. MDX options will default to their equivalent in your Markdown config. By setting extendMarkdownConfig to false, you can “eject” to set your own syntax highlighting, plugins, and more.To preserve your existing Markdown and MDX setup, you may need some configuration changes:
Smartypants has been removed from Astro’s default setup. If you rely on this plugin, install remark-smartypants and apply to your astro.config.*:
import { defineConfig } from 'astro/config'; import smartypants from 'remark-smartypants';
export default defineConfig({ markdown: { remarkPlugins: [smartypants], }});extendDefaultPlugins to gfmYou may have disabled Astro’s built-in plugins (GitHub-Flavored Markdown and Smartypants) with the extendDefaultPlugins option. Since Smartypants has been removed, this has been renamed to gfm.
import { defineConfig } from 'astro/config';
export default defineConfig({ markdown: { extendDefaultPlugins: false, gfm: false, }});Additionally, applying remark and rehype plugins no longer disables gfm. You will need to opt-out manually by setting gfm to false.
extendPlugins to extendMarkdownConfigYou may have used the extendPlugins option to manage plugin defaults in MDX. This has been replaced by 2 flags:
extendMarkdownConfig (true by default) to toggle Markdown config inheritance. This replaces the extendPlugins: 'markdown' option.gfm (true by default) to toggle GitHub-Flavored Markdown in MDX. This replaces the extendPlugins: 'defaults' option.#5654 2c65b433b Thanks @delucis! - Run heading ID injection after user plugins
⚠️ BREAKING CHANGE ⚠️
If you are using a rehype plugin that depends on heading IDs injected by Astro, the IDs will no longer be available when your plugin runs by default.
To inject IDs before your plugins run, import and add the rehypeHeadingIds plugin to your rehypePlugins config:
import { rehypeHeadingIds } from '@astrojs/markdown-remark';import mdx from '@astrojs/mdx';
export default { integrations: [mdx()], markdown: { rehypePlugins: [ rehypeHeadingIds, otherPluginThatReliesOnHeadingIDs, ], },}#5667 a5ba4af79 Thanks @bholmesdev! - Chore: remove verbose “Now interiting Markdown plugins…” logs
#5648 853081d1c Thanks @bholmesdev! - Prevent relative image paths in src/content/
Updated dependencies [853081d1c, 2c65b433b]:
5ec0f6ed5 Thanks @bholmesdev! - Introduce Content Collections experimental API
308e565ad Thanks @bholmesdev! - Support recmaPlugins config option#4700 e5f71142e Thanks @bholmesdev! - Document MDXLayoutProps utility type
#4858 58a2dca22 Thanks @bholmesdev! - Correctly parse import.meta.env in MDX files
db38f61b2 Thanks @bholmesdev! - Fix: Add GFM and Smartypants to MDX by default8f8dff4d3 Thanks @bholmesdev! - Introduce new extendPlugins configuration option. This defaults to inheriting all remark and rehype plugins from your markdown config, with options to use either Astro’s defaults or no inheritance at all.d4cd7a59f Thanks @bholmesdev! - Update Markdown type signature to match new markdown plugin,and update top-level layout props for better alignmentd4cd7a59f Thanks @bholmesdev! - Update Markdown type signature to match new markdown plugin,and update top-level layout props for better alignment#4443 adb207979 Thanks @bholmesdev! - Fix MDX style imports when layout is not applied
#4428 a2414bf59 Thanks @bholmesdev! - Fix dev server reload performance when globbing from an MDX layout
f1a52c18a Thanks @bholmesdev! - Switch from Shiki Twoslash to Astro’s Shiki Markdown highlighter