Our Astro source build passed in 91 seconds, and its test command exited 1 after 57 seconds. Astro belongs on the shortlist for portfolios, publications and client sites with selected interactive components. If retaining an Emotion-based interface unchanged is essential, assess SSR compatibility on your intended versions before choosing Astro: Coobaha's RapidAPI evaluation in issue #4432 documents a historical migration blocker.
The framework decision also includes the editing system. A developer maintaining a portfolio can edit source files directly; a client placing images beside text needs an authoring interface that supports that task. This review connects the source-run results with named portfolio reports, a CMS discussion and version-specific integration failures, so those decisions have concrete evidence behind them.
What people use Astro for
Developers report completed portfolios and an EmDash-backed website, while RapidAPI's account describes an SSR evaluation. Those are different outcomes: the portfolio reports describe work people shipped, and the compatibility thread describes a dependency that affected a migration decision. The examples below identify the person, task and reported result rather than treating every mention of Astro as evidence of adoption.
| Who used it | What they did | Reported outcome |
|---|---|---|
| thekwoka on r/webdev | Built a portfolio with server-rendered SVG routes cached on Cloudflare | Reported a simple implementation and quick route loading in the portfolio discussion. |
| TypicalFeed6823 on r/webdev | Built a personal portfolio | Described a fast development experience in the portfolio discussion. |
| AriadneOpsSocial on r/astrojs | Built AllPlayful.com with EmDash as the admin | Described WordPress-like flexibility in the CMS discussion. |
| Coobaha, reporting an evaluation at RapidAPI | Evaluated SSR with an Emotion-based UI library | Identified a major compatibility blocker in the CSS-in-JS discussion. |
The SVG portfolio gives a specific example of server rendering: an image is generated through a route and cached on Cloudflare. AllPlayful.com illustrates a different choice, pairing the website with an administration interface. For readers considering that arrangement, the existing EmDash overview addresses the CMS itself; this page addresses choosing Astro alongside an editor and existing integrations.
What happened when we ran it
Our October 26 run installed commit e5a3a1b in 56 seconds, built it in 91 seconds and reached a failed test command after 57 seconds. The source-run measurements describe a pnpm contributor workspace with 7,012 files, approximately 277,034 source lines and a 51.9 MB checkout. Its recorded sandbox configuration was 3 CPUs, 8 GB RAM and image lab-node:22.
| October source-run step | Recorded result |
|---|---|
| Install | Succeeded in 56 seconds; 1,936 dependencies recorded |
| Installed disk footprint | 1,345 MB |
| Build | Succeeded in 91 seconds |
| Tests | Failed, exit 1, after 57 seconds |
| Repository scan | 23 CI workflow files; monorepo workspaces; no Dockerfile or tests directory detected |
The test tail contains six named passing checks: rejecting an over-encoded path with a 400 response instead of reaching /api/admin; merging workerd into allowBuilds rather than passing --allow-build; reporting a failing thunk while continuing on the unswapped logger; creating a response that bypasses the page; dropping Content-Length for a rendered 404; and dropping Transfer-Encoding for a rendered 500. The same recorded output then prints failing-tests and lifecycle failure messages.
The separate November 20 quickstart record identifies repository commit c302892e4a24, recipe quickstart-lib and a fresh, unprivileged lab-node:22 container with 2 CPUs, 4 GB RAM, no published ports and no secrets. Its clone step took 3 seconds. The installation command was npm install astro@latest, while the README's manual command omits @latest.
| November quickstart step | Recorded result |
|---|---|
| Clone | Recipe quickstart-lib; 3 seconds |
| Install | Astro 7.4.13 installed in 57 seconds |
| Installed size | 202.7 MB in node_modules |
| Dependency count | 197 packages besides Astro |
| Application snippet | Failed: no JavaScript/TypeScript code block in the README |
| Teardown | Completed successfully |
The package installation recorded Astro 7.4.13 and 57 seconds, followed by 202.7 MB on disk and 197 packages besides Astro. The snippet step failed for the reason also recorded as the no-snippet finding. The teardown record says it completed. Installation therefore succeeded before the recipe stopped at application-example execution.
Where people get stuck: development and production differ
Issue #16181 reports component styles missing in development after an Astro 5-to-6 upgrade while built output contained the styles. Its environments include Astro 6.1.2, with subsequent reports through 6.1.8. The CSS regression discussion includes a maintainer recommendation to stay on Astro 5 temporarily and a user's workaround of moving affected styles into global CSS.
| Report | What happened | Response documented in the discussion |
|---|---|---|
| #4432, CSS-in-JS | Historical Emotion and styled-components SSR problems included styled.div is not a function | Client-only rendering and library-specific workarounds, sometimes with a flash of unstyled content. |
| #5211, Telefunc | Astro 1.6.0 development worked; production bundling failed with id.endsWith is not a function | Investigation of Rollup input merging and configuration. |
| #9345, Sharp | Astro 3.6.4 and 4.0.2 builds failed after Sharp 0.33.0 upgrades while development worked | Reports of success with Sharp 0.32.x or installation changes. |
| #10668, Astro DB and Cloudflare | Remote builds failed while bundling the Node url built-in | Node compatibility and externalizing url worked for two participants. |
These reports give concrete investigation paths. Missing development CSS and failed production bundling are different symptoms, even when the local page looks similar. Compare development output with a built preview, preserve the first error and record the core, adapter and integration versions together. The Cloudflare database discussion also identifies a configuration requirement: its token was needed during both building and deployed execution.
Large Markdown sites need a build-memory budget
Issue #10485 describes an out-of-memory static build with more than 100,000 Markdown files on Astro 4.5.6. Maintainer matthewp explained that files become JavaScript modules and Rollup retains those modules in memory together. The archive-build discussion also includes a separate 10,000-plus-file report where setting a 24 GB heap allowed completion, with a reported 17 GB peak and roughly 16 GB stable usage.
Those figures make archive size a deployment planning input. Include representative Markdown, MDX, images and integrations when estimating the builder's memory needs. The maintainer described the reported constraint as architectural, and the successful larger-heap report describes a resource workaround. Astro's rendering overview also describes server rendering and on-demand rendering, giving teams another rendering choice to evaluate alongside static generation.
Client editing includes image placement
Ceewise's move from WordPress toward Astro raised a specific CMS requirement: left- or right-aligned images with text wrapping around them. The question named difficulty doing this in Pages CMS. In the client-editing discussion, EmDash contributor danielovida described alignment settings, wrapping in the editor and built-in PortableText rendering; custom image components would need to handle the alignment field themselves.
Use that task when selecting the editing system: place an image beside a paragraph, change its caption, inspect the mobile presentation and publish a correction. These are proposed acceptance tasks. They connect the client's requirement to an observable result, rather than assuming that Markdown support settles authoring usability. AriadneOpsSocial's completed AllPlayful.com report supplies a named EmDash example, and the discussion separately contains a community pointer to Docker deployment documentation.
Rendering boundaries explain inert components
Astro's troubleshooting guide says framework components render on the server by default and need an appropriate client directive for browser interaction. Hydration attaches browser behavior to the rendered HTML. The framework-component guidance therefore distinguishes a component appearing on the page from that component responding to input, a useful distinction when reusing a React or Svelte widget.
The same guide explains that accessing document or window on the server causes errors. Its documented approaches include placing Astro browser code in a script tag, using framework lifecycle methods with hydration, or choosing client:only where appropriate. These choices affect where code executes. They also explain why copying a browser-dependent component into a rendered page can require more than its import statement.
Security checks in the test tail are specific
The October test tail records a passing over-encoded-path check returning 400 instead of bypassing to /api/admin, plus passing response-header checks for 404 and 500 pages. The test output records these individual outcomes alongside the overall exit 1. The repository scan's absence of a tests directory is a directory-detection result; the command output itself contains executed test cases.
A separate historical middleware report, issue #8191, describes missing middleware execution and locals. Maintainers initially saw the expected log in the reproduction, while a later investigation found an empty middleware artifact after adding an adapter. For a site with private content, include unauthenticated requests, middleware behavior and error responses in deployment acceptance work. That recommendation follows the reported failure surface and the specific checks visible in our run.
Astro vs Next.js, React, WordPress and Vite
Next.js describes full-stack React applications, while Astro's documented model combines rendered content with selected interactive components. That supports a practical shortlist based on the site's interaction requirements and editing workflow. The Next.js README establishes its React application focus; Astro's rendering overview explains its island model and distinguishes frameworks from build tools.
| Choice | When it belongs on your shortlist | Decision to make |
|---|---|---|
| Astro vs Next.js | Astro for content with isolated interaction; Next.js for a React application with substantial shared state | Identify which interactions coordinate across the screen. |
| Astro vs React | Astro can render React components within its pages | Choose which components need browser hydration. |
| Astro vs WordPress | An Astro migration includes selecting the authoring workflow | Have editors complete their required CMS tasks. |
| Astro vs Vite | Astro is a framework; Vite is a build tool | Decide whether the project needs Astro's rendering conventions. |
The WordPress comparison comes from a developer's migration question and the EmDash responses, rather than a feature-count contest. The Vite distinction is similarly concrete: Telefunc's historical report describes development working and Astro production bundling failing. A framework selection includes the production integration path as well as the development tool. For React components, the official troubleshooting guide makes hydration an explicit part of that path.
What the other reviews get wrong
Cipher Projects' March 2, 2026 comparison presents Astro 5 as current, while issue #16181 contains Astro 6 environments. Its Next.js versus Astro comparison therefore has dated version framing relative to those reports. Package identity also matters when reading releases: the repository metadata lists @astrojs/node@11.1.14 on November 18, 2026, which identifies an adapter release rather than an Astro core version.
The comparison also describes Astro data fetching as a build-time approach. That description is incomplete: Devlune's rendering overview explicitly includes HTML rendering at build time or on the server, plus on-demand rendering and personalized server islands. Build-time execution is one supported mode. A page requiring request-specific content calls for a rendering and hosting decision, rather than excluding Astro on the basis of that comparison paragraph.
FAQ
Astro's official tutorial starts with basic HTML, Markdown, CSS and a little JavaScript, while its README recommends npm create astro@latest for project creation. The questions below come from tutorial prompts, search questions and developer discussions. They address the first project, the client editing workflow and historical installation trouble, with answers tied to the particular documentation or report.
Is Astro a good choice for a small client website, and what are its practical pros and cons?
Developers in the small-site discussion report completed portfolios and positive development experiences. For a client website, the CMS is another selection: Ceewise's editing question identifies image alignment and wrapping as concrete requirements. Astro is a reasonable candidate when its rendering model fits the pages and the chosen editing interface lets the client perform those tasks.
Should I choose Astro or Next.js for SEO and a content-heavy website?
Astro's rendering overview describes HTML output with selected interactive islands, while the Next.js README describes full-stack React applications. Choose between those models using the site's content and interaction requirements. A portfolio user's quick-loading report describes that person's website; it supplies a concrete deployment account rather than a reason to promise improved search rankings.
Which CMS works well with Astro for production client websites?
AriadneOpsSocial reports using EmDash as the admin for AllPlayful.com and describes it as flexible like WordPress in the CMS discussion. That gives readers a named completed-site example. The same discussion makes image placement a useful selection task: the editor, content renderer and any custom image component must agree on how alignment settings affect the published page.
Can an Astro CMS editor align images left or right with text wrapping around them?
EmDash contributor danielovida describes left, center and right alignment, with left and right floating the image so text wraps around it. The alignment reply also describes built-in PortableText rendering and says a custom image component must handle the alignment field itself. This answer concerns the EmDash workflow discussed in response to Ceewise's Pages CMS question.
What do I need to know before learning Astro?
The official tutorial introduction asks for basic familiarity with HTML, Markdown, CSS and a little JavaScript, plus a GitHub or similar account for publishing. Its first-page lesson then teaches creating about.astro under src/pages, adding About and Blog pages, linking between them and deploying an updated website. Those steps provide a documented route beyond package installation.
Why does create-astro fail or get stuck on Windows?
Historical issue #5227 records failed file copying, repeated prompt behavior and a non-TTY setRawMode error. Manual installation worked for the original reporter. Fresh App Factory's maintainer also reported daily generator automation working with create-astro 1.1.0 and breaking after 1.2.0. Match the observed error and generator version to the report before adopting one of its installation workarounds.
What we have not tested yet
The October run measures contributor installation, compilation and a failed test command; the November run measures package installation and a stopped snippet recipe. Neither measures visitor speed, search rankings, editor usability or deployed-site reliability. The October image label does not identify the actual Node or operating-system version, and its test tail omits the failing assertion, complete totals and cause. No vulnerability audit accompanies that run.
Current Emotion SSR compatibility, the historical integration workarounds and the reported Astro 6 CSS behavior require assessment on the intended core, adapter and dependency versions. Issue closure alone does not demonstrate a fix across those combinations. We have not reproduced the large archive builds, tested EmDash or Pages CMS, migrated an Emotion library, or exercised private routes on a deployed adapter. The CMS replies do not demonstrate a repaired Pages CMS workflow or Ceewise's completed switch.
The November check executed no application snippet or browser interaction, and its resource figures must stay separate from the October contributor measurements. Astro 7.4.13 identifies the npm package installed in that check; it is not a release identification for the October source commit. This review also contains no matched-site Next.js benchmark or direct Hugo, SvelteKit or Webflow trial. Relevant social and search records establish neither worldwide demand nor ranking, and unrelated Astro entities provide no framework evidence.


