🐞 Patch Changes
- #7185
339529fc8Thanks @bholmesdev! - Bring back improved style and script handling across content collection files. This addresses bugs found in a previous release to@astrojs/markdoc.
@astrojs/mdx
🐞 Patch Changes
- #7178
57e65d247Thanks @bholmesdev! - Fix: revert Markdoc asset bleed changes. Production build issues were discovered that deserve a different fix.
- #7178
🐞 Patch Changes
- #6758
f558a9e20Thanks @bholmesdev! - Improve style and script handling across content collection files. This addresses style bleed present in@astrojs/markdocv0.1.0
- #6758
🍿 Minor Changes
- #6824
2511d58d5Thanks @Princesseuh! - Add support for using optimized and relative images in MDX files withexperimental.assets
🐞 Patch Changes
- Updated dependencies [
2511d58d5]:- @astrojs/markdown-remark@2.1.4
- #6824
🐞 Patch Changes
- #6817
f882bc163Thanks @bholmesdev! - Fix sourcemap warnings when using Content Collections and MDX with thevite.build.sourcemapoption
- #6817
🐞 Patch Changes
-
#6494
a13e9d7e3Thanks @Yan-Thomas! - Consistency improvements to several package descriptions -
Updated dependencies [
a13e9d7e3]:- @astrojs/prism@2.1.1
-
🍿 Minor Changes
-
#6344
694918a56Thanks @Princesseuh! - Add a new experimental flag (experimental.assets) to enable our new core Assets story.This unlocks a few features:
- A new built-in image component and JavaScript API to transform and optimize images.
- Relative images with automatic optimization in Markdown.
- Support for validating assets using content collections.
- and more!
See Assets (Experimental) on our docs site for more information on how to use this feature!
-
#6213
afbbc4d5bThanks @Princesseuh! - Updated compilation settings to disable downlevelling for Node 14
🐞 Patch Changes
-
#6209
fec583909Thanks @bholmesdev! - Introduce the (experimental)@astrojs/markdocintegration. This unlocks Markdoc inside your Content Collections, bringing support for Astro and UI components in your content. This also improves Astro core internals to make Content Collections extensible to more file types in the future.You can install this integration using the
astro addcommand:astro add markdocRead the
@astrojs/markdocdocumentation for usage instructions, and browse the newwith-markdocstarter to try for yourself. -
Updated dependencies [
694918a56,afbbc4d5b]:- @astrojs/markdown-remark@2.1.0
- @astrojs/prism@2.1.0
-
🐞 Patch Changes
- #6296
075b87e8bThanks @RaphaelBossek! - Update toes-module-lexer@1.1.1
- #6296
🍿 Minor Changes
- #6253
0049fda62Thanks @bluwy! - Support rehype plugins that inject namespaced attributes. This introduces a breaking change if you use custom components for HTML elements, where the prop passed to the component will be normal HTML casing, e.g.classinstead ofclassName, andxlink:hrefinstead ofxlinkHref.
- #6253
🍿 Minor Changes
-
#5684
a9c292026Thanks @bholmesdev! - Refine Markdown and MDX configuration options for ease-of-use. & #576993e633922Thanks @bholmesdev! - Introduce asmartypantsflag to opt-out of Astro’s default SmartyPants plugin.-
Markdown
- Replace the
extendDefaultPluginsoption with agfmboolean and asmartypantsboolean. These are enabled by default, and can be disabled to remove GitHub-Flavored Markdown and SmartyPants. - Ensure GitHub-Flavored Markdown and SmartyPants are applied whether or not custom
remarkPluginsorrehypePluginsare configured. If you want to apply custom plugins and remove Astro’s default plugins, manually setgfm: falseandsmartypants: falsein your config.
- Replace the
-
Migrate
extendDefaultPluginstogfmandsmartypantsYou may have disabled Astro’s built-in plugins (GitHub-Flavored Markdown and Smartypants) with the
extendDefaultPluginsoption. This has now been split into 2 flags to disable each plugin individually:-
markdown.gfmto disable GitHub-Flavored Markdown -
markdown.smartypantsto disable SmartyPantsastro.config.mjs import { defineConfig } from 'astro/config';export default defineConfig({markdown: { -
extendDefaultPlugins: false,
-
smartypants: false,
-
gfm: false, } });
Additionally, applying remark and rehype plugins **no longer disables** `gfm` and `smartypants`. You will need to opt-out manually by setting `gfm` and `smartypants` to `false`.
-
-
MDX
-
Support all Markdown configuration options (except
drafts) from your MDX integration config. This includessyntaxHighlightingandshikiConfigoptions to further customize the MDX renderer. -
Simplify
extendPluginsto anextendMarkdownConfigoption. MDX options will default to their equivalent in your Markdown config. By settingextendMarkdownConfigto false, you can “eject” to set your own syntax highlighting, plugins, and more.
-
-
Migrate MDX’s
extendPluginstoextendMarkdownConfigYou may have used the
extendPluginsoption to manage plugin defaults in MDX. This has been replaced by 3 flags:extendMarkdownConfig(trueby default) to toggle Markdown config inheritance. This replaces theextendPlugins: 'markdown'option.gfm(trueby default) andsmartypants(trueby default) to toggle GitHub-Flavored Markdown and SmartyPants in MDX. This replaces theextendPlugins: 'defaults'option.
-
-
#5687
e2019be6fThanks @bholmesdev! - Give remark and rehype plugins access to user frontmatter via frontmatter injection. This meansdata.astro.frontmatteris 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
imageSrcslug 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;};}When using Content Collections, you can access this modified frontmatter using the
remarkPluginFrontmatterproperty returned when rendering an entry.Migration instructions
Plugin authors should now check for user frontmatter when applying defaults.
For example, say a remark plugin wants to apply a default
titleif 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.
-
#5891
05caf445dThanks @bholmesdev! - Remove deprecated Markdown APIs from Astro v0.X. This includesgetHeaders(), the.astroproperty for layouts, and therawContent()andcompiledContent()error messages for MDX. -
#5782
1f92d64eaThanks @Princesseuh! - Remove support for Node 14. Minimum supported Node version is now >=16.12.0 -
#5825
52209ca2aThanks @bholmesdev! - Baseline the experimentalcontentCollectionsflag. You’re free to remove this from your astro config!import { defineConfig } from 'astro/config';export default defineConfig({experimental: { contentCollections: true }})
🐞 Patch Changes
-