create-astro
✨ Major Changes
- #14427
e131261Thanks @florian-lefebvre! - Increases minimum Node.js version to 22.12.0 - (v6 upgrade guidance)
- #14427
🐞 Patch Changes
- #14528
3597371Thanks @florian-lefebvre! - Fixes a case where a deprecation warning would be shown on Node 24
- #14528
🐞 Patch Changes
- #14158
89e9364Thanks @bjohansebas! - Prevents deprecation warnings in Node 24
- #14158
🍿 Minor Changes
-
#14115
270e009Thanks @ascorbic! - Removes “Open in x” badges from the README of the official Astro templates when a new project is created -
#14115
270e009Thanks @ascorbic! - Adds support for marking sections in template READMEs to be removed when thecreate astrocommand is used to create a new projectTheme authors can now use magic comments in template READMEs to mark sections that should not be included when a user runs
create-astrowith the--templateflag to create a new project.This allows templates to have content that is visible when viewed in the source repo but not when the template is copied for use in a new project. This is useful for content that is appropriate for a theme’s own repository, but will not be useful to someone using the theme, such as an “Open this repository in StackBlitz” badge where the URL is hardcoded .
Use the magic comments
<!-- ASTRO:REMOVE:START -->and<!-- ASTRO:REMOVE:END -->to indicate content to be excluded from your README during thecreate astroprocess.<!-- ASTRO:REMOVE:START -->[](https://stackblitz.com/github/withastro/astro/tree/latest/examples/basics)<!-- ASTRO:REMOVE:END -->Note that these comments only remove content when new projects are created using
create astro. When your theme template is forked, your README will be copied in its entirety.
-
🐞 Patch Changes
- #12529
485c2f0Thanks @apatel369! - Fixes an issue where installing Astro beta usingcreate-astrodisplays the wrong Astro version in the installation messages.
- #12529
🍿 Minor Changes
-
#13809
3c3b492Thanks @ascorbic! - Increases minimum Node.js version to 18.20.8Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro’s Node.js support policy for more details.
:warning: Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.
-
🐞 Patch Changes
- #13591
5dd2d3fThanks @florian-lefebvre! - Removes unused code
- #13591
🐞 Patch Changes
- #13636
a9fd03fThanks @sarah11918! - Updates the wording for choosing the “minimal” starter template options
- #13636
🍿 Minor Changes
-
#12083
9263e96Thanks @Princesseuh! - Reworks the experience of creating a new Astro project using thecreate astroCLI command.- Updates the list of templates to include Starlight and combines the “minimal” and “basics” templates into a new, refreshed “Basics” template to serve as the single, minimal Astro project starter.
- Removes the TypeScript question. Astro is TypeScript-only, so this question was often misleading. The “Strict” preset is now the default, but it can still be changed manually in
tsconfig.json. astro checkis no longer automatically added to the build script.- Added a new
--addflag to install additional integrations after creating a project. For example,pnpm create astro --add reactwill create a new Astro project and install the React integration.
🍿 Minor Changes
-
#12083
9263e96Thanks @Princesseuh! - Reworks the experience of creating a new Astro project using thecreate astroCLI command.- Updates the list of templates to include Starlight and combines the “minimal” and “basics” templates into a new, refreshed “Basics” template to serve as the single, minimal Astro project starter.
- Removes the TypeScript question. Astro is TypeScript-only, so this question was often misleading. The “Strict” preset is now the default, but it can still be changed manually in
tsconfig.json. astro checkis no longer automatically added to the build script.- Added a new
--addflag to install additional integrations after creating a project. For example,pnpm create astro --add reactwill create a new Astro project and install the React integration.
-
🍿 Minor Changes
- #11924
7d70ba3Thanks @florian-lefebvre! - Updates the default Astro config with// @ts-checkif the Typescript preset isstrictorstrictest
- #11924