Skip to content

[docs] Update Astro dependencies - 2026-06-24 #41258

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pelikhan merged 3 commits into from
Jun 24, 2026
+1,143 −640
Merged

[docs] Update Astro dependencies - 2026-06-24 #41258

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c9ec31a
[docs] Update Astro dependencies - 2026-06-24
github-actions[bot] Jun 24, 2026
d803bf6
Pin @astrojs/markdown-remark to 7.2.0 in docs
Copilot Jun 24, 2026
c2d863d
Merge branch 'main' into docs/update-astro-2026-06-24-bd52264ed296cf43
pelikhan Jun 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions docs/astro.config.mjs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@ import starlightGitHubAlerts from 'starlight-github-alerts';
import starlightBlog from 'starlight-blog';
import mermaid from 'astro-mermaid';
import { fileURLToPath } from 'node:url';
import { unified } from '@astrojs/markdown-remark';

@github-actions github-actions Bot Jun 24, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

unified is also the name of the popular unified npm package, so this import will confuse developers familiar with the remark/rehype ecosystem but not yet with Astro 7's new processor API.

💡 Suggested fix

Add a clarifying comment or alias to make the origin unmistakable:

// unified() is `@astrojs/markdown-remark`'s processor factory, not the unified npm package
import { unified } from '`@astrojs/markdown-remark`';

or use an alias:

import { unified as createMarkdownProcessor } from '`@astrojs/markdown-remark`';
// ...
processor: createMarkdownProcessor({ remarkPlugins: [...], rehypePlugins: [...] }),

This removes the guesswork about which unified this is and avoids a naming collision if the actual unified package is ever imported for a custom plugin.

import remarkStripEmojis from './src/lib/remark/stripEmojis.js';
import remarkTableDataLabels from './src/lib/remark/tableDataLabels.js';
import rehypeTableWrapper from './src/lib/rehype/tableWrapper.js';
Expand Down Expand Up @@ -37,8 +38,10 @@ export default defineConfig({
base: '/gh-aw/',
trailingSlash: 'always',
markdown: {
remarkPlugins: [remarkStripEmojis, remarkTableDataLabels],
rehypePlugins: [rehypeTableWrapper],
processor: unified({
remarkPlugins: [remarkStripEmojis, remarkTableDataLabels],
rehypePlugins: [rehypeTableWrapper],
}),
},
vite: {
server: {
Expand Down
Loading
Loading