Releases: hashicorp/remark-plugins
3.3.0
This release adds support for a new headings
option in the anchor-links
plugin.
See PR #38 or the Options section of the anchor-links
README for full details.
3.2.2
3.2.1
This release removes the alert role from the custom alert remark plugin to create a better experience for folks using screen readers.
3.2.0
feat(include-markdown): support MDX custom components
This release adds support for custom components in partials @include
'd using the include-markdown
plugin.
This feature can be enabled by passing { resolveMdx: true }
to the include-markdown
plugin's options. For example, using next-mdx-remote
, you might call serialize
like:
const mdxSource = await serialize(source, {
mdxOptions: {
remarkPlugins: [[includeMarkdown, { resolveMdx: true }]],
},
})
For further details, see #28 .
3.1.1
This release fixes a minor issue where empty strings passed to the typography
plugin would not trigger the expected behaviour of omitting a typography class from the target element. This release also includes some documentation changes.
3.1.0
[canary] Expose typography options in allPlugins
Patches
- Expose typography options in allPlugins: 91552bd
[canary] Add map option to typography plugin
3.0.0
This release adds a feature to the include-markdown
plugin, for which any file with a .md
or .mdx
extension will behave identically, but files with any other extension will be included as plaintext, within a code block.
This is marked as major, as it could potentially be breaking if you were including markdown content from files with an extension that is not .md
or .mdx
.
Details in #14