Upgrade to Astro 7 - #26
Merged
Merged
Conversation
Bump astro 6.1.7 to 7.1.1 and companion packages: @astrojs/mdx to 7, @astrojs/preact to 6, astro-expressive-code to 0.44 (first release with an Astro 7 peer), astro-tunnel to 0.1.9, @astrojs/rss to 4.0.19. Add @astrojs/markdown-remark 7.2.1 explicitly since the blog pages import createMarkdownProcessor directly. Astro 7's new MDX processor (Satteri) rejects a JSX opening tag whose '>' starts its own line after multi-line attributes. Reflow the gradient demo divs in colors-in-css.mdx so each '>' ends the attribute line. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
✅ Deploy Preview for mcssdev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
`npm ci` on CI (Node 22 / npm 10) rejected the lock file generated locally by npm 11: it computed a different ideal tree and reported sugarss@5.0.1 and the emnapi wasm-fallback packages as missing. Regenerate the lock with npm 10 so it matches CI's resolution. Verified with `npm@10 ci --dry-run` (exit 0) and the full CI sequence (check, lint:css, build, build:css) passing locally. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The previous lock regenerations ran with node_modules present, so npm reused the local (macOS) tree and wrote a darwin-only lock: rolldown, satteri, and esbuild lost their linux/windows optional bindings, and CI's npm ci failed with "Cannot find module '@rolldown/binding-linux-x64-gnu'". Removing both node_modules and package-lock.json and reinstalling resolves purely from the registry, which records the full platform matrix (26 esbuild platforms, matching the pre-upgrade lock). Verified: npm@10 ci --dry-run exits 0, and check / lint:css / build / build:css all pass against the fresh tree. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Upgrades the docs site from Astro 6.1.7 to Astro 7.1.1 (a major version jump).
Version bumps (
package.json):astro6.1.7 → 7.1.1@astrojs/mdx5 → 7,@astrojs/preact5 → 6astro-expressive-code0.41 → 0.44 (first release declaring an Astro 7 peer)astro-tunnel0.1.8 → 0.1.9,@astrojs/rss4.0.18 → 4.0.19@astrojs/markdown-remark7.2.1. The blog list pages importcreateMarkdownProcessordirectly, but it was an undeclared transitive dependency. Pinning it keeps that usage from drifting from Astro's copy.Content fix (
src/content/blog/colors-in-css.mdx):Astro 7's new default MDX processor (Satteri, Rust-based) rejects a JSX opening tag whose
>starts its own line after multi-line attributes, which is prettier's default multi-line JSX formatting. Reflowed the gradient-demo divs so each>ends the attribute line. This was the only build breakage across all 50 MDX files.Why
Answering "does upgrading to the latest Astro break anything?" The site was already past the usual pain points for an Astro major (Content Layer API, no view transitions, middleware, actions, DB, or experimental flags), so this is mostly coordinated version bumps plus the one MDX parser fix.
Verification
astro build: 100 pages, no errors.astro check: 0 errors.@layercascade order intact in the bundled site CSS. Vite 8 drops the redundant standalone@layer ...;declaration but preserves block order, so layer priority is unchanged. Thedist/mcss.cssartifact frombuild:cssis untouched (still carries the explicit declaration).astro:assetsimages optimize (6 → webp/svg).client:visible, range sliders live). No console or server errors.Notes for reviewer
compressHTMLnow defaults to JSX-style whitespace collapse. Left at the default. If inline spacing looks off anywhere, setcompressHTML: trueinastro.config.mjs.peerOptionalwarning (from postcss-mixins) and a dual-Vite (7.3.1 hoisted from@preact/preset-vitealongside Astro's own Vite 8). The build uses Vite 8; both are cosmetic.🤖 Generated with Claude Code