public-backup/astro
1
0
Fork 0
mirror of https://github.com/withastro/astro.git synced 2025-12-05 18:56:38 -06:00
Code Issues Packages Projects Releases Wiki Activity
Files
main
astro/packages/create-astro/CHANGELOG.md
Houston (Bot) ef7af66097 [ci] release (#14527) 
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2025-10-14 15:08:21 +02:00

43 KiB
Raw Permalink Blame History

create-astro

4.13.2

Patch Changes

4.13.1

Patch Changes

4.13.0

Minor Changes

  • #14115 270e009 Thanks @ascorbic! - Removes "Open in x" badges from the README of the official Astro templates when a new project is created

  • #14115 270e009 Thanks @ascorbic! - Adds support for marking sections in template READMEs to be removed when the create astro command is used to create a new project

    Theme authors can now use magic comments in template READMEs to mark sections that should not be included when a user runs create-astro with the --template flag 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 the create astro process.

    <!-- ASTRO:REMOVE:START -->

[![Open in StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](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.

4.12.1

Patch Changes

  • #12529 485c2f0 Thanks @apatel369! - Fixes an issue where installing Astro beta using create-astro displays the wrong Astro version in the installation messages.

4.12.0

Minor Changes

  • #13809 3c3b492 Thanks @ascorbic! - Increases minimum Node.js version to 18.20.8

    Node.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.

    ⚠️ 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.

4.11.4

Patch Changes

4.11.3

Patch Changes

4.11.2

Patch Changes

4.11.1

Patch Changes

  • #13257 6012e06 Thanks @ADTC! - Modify the template README file to reflect the correct package manager

4.11.0

Minor Changes

  • #12539 827093e Thanks @bluwy! - Drops node 21 support

  • #12083 9263e96 Thanks @Princesseuh! - Reworks the experience of creating a new Astro project using the create astro CLI 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 check is no longer automatically added to the build script.
    • Added a new --add flag to install additional integrations after creating a project. For example, pnpm create astro --add react will create a new Astro project and install the React integration.

4.11.0-beta.1

Minor Changes

4.11.0-beta.0

Minor Changes

  • #12083 9263e96 Thanks @Princesseuh! - Reworks the experience of creating a new Astro project using the create astro CLI 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 check is no longer automatically added to the build script.
    • Added a new --add flag to install additional integrations after creating a project. For example, pnpm create astro --add react will create a new Astro project and install the React integration.

4.10.0

Minor Changes

  • #12154 9988dd6 Thanks @bluwy! - Improves default template download speed by downloading from a branch containing the template only

  • #12186 49c4f64 Thanks @Terfno! - Ensures new line at the end of the generated package.json and tsconfig.json files

4.9.2

Patch Changes

  • #12143 2385d58 Thanks @bluwy! - Uses @bluwy/giget-core instead of giget for smaller installation size when downloading the CLI

4.9.1

Patch Changes

4.9.0

Minor Changes

4.8.4

Patch Changes

4.8.3

Patch Changes

4.8.2

Patch Changes

  • #11645 849e4c6 Thanks @bluwy! - Refactors internally to use node:util parseArgs instead of arg

4.8.1

Patch Changes

4.8.0

Minor Changes

4.7.5

Patch Changes

4.7.4

Patch Changes

4.7.3

Patch Changes

4.7.2

Patch Changes

4.7.1

Patch Changes

4.7.0

Minor Changes

4.6.0

Minor Changes

4.5.2

Patch Changes

4.5.2-beta.0

Patch Changes

4.5.1

Patch Changes

  • #9048 1e97708cd Thanks @skirianov! - Fixes an issue where a successful "Dependencies installed" message is displayed even when installing dependencies fails.

4.5.0

Minor Changes

Patch Changes

4.4.1

Patch Changes

  • #8911 b236d88ad Thanks @natemoo-re! - Ensure an existing template's package.json scripts are respected when modifying build.

4.4.0

Minor Changes

  • #8853 ce807a2bf Thanks @rayriffy! - Automatically installs the required dependencies to run the astro check command when the user indicates they plan to write TypeScript.

Patch Changes

  • #8841 f2dd895d7 Thanks @Genteure! - No longer attempts to delete the directory after a template download fails if the path is ., ./ or starts with ../.

4.3.0

Minor Changes

4.2.1

Patch Changes

4.2.0

Minor Changes

4.1.0

Minor Changes

  • #8456 ed952b4ce Thanks @natemoo-re! - Improve startup performance by removing dependencies, lazily initializing async contextual values

4.0.2

Patch Changes

4.0.1

Patch Changes

4.0.0

Major Changes

  • #8188 d0679a666 Thanks @ematipico! - Remove support for Node 16. The lowest supported version by Astro and all integrations is now v18.14.1. As a reminder, Node 16 will be deprecated on the 11th September 2023.

  • #8179 6011d52d3 Thanks @matthewp! - Astro 3.0 Release Candidate

4.0.0-rc.2

Major Changes

4.0.0-beta.1

Patch Changes

4.0.0-beta.0

Major Changes

  • 1eae2e3f7 Thanks @Princesseuh! - Remove support for Node 16. The lowest supported version by Astro and all integrations is now v18.14.1. As a reminder, Node 16 will be deprecated on the 11th September 2023.

3.2.2

Patch Changes

3.2.1

Patch Changes

3.2.0

Minor Changes

3.1.13

Patch Changes

3.1.12

Patch Changes

3.1.11

Patch Changes

3.1.10

Patch Changes

3.1.9

Patch Changes

  • #7527 9e2426f75 Thanks @natemoo-re! - Default registry logic to fallback to NPM if registry command fails (sorry, Bun users!)

  • #7539 1170877b5 Thanks @jc1144096387! - Update registry logic, improving edge cases (http support, redirects, registries ending with '/')

3.1.8

Patch Changes

3.1.7

Patch Changes

3.1.6

Patch Changes

3.1.5

Patch Changes

3.1.4

Patch Changes

3.1.3

Patch Changes

3.1.2

Patch Changes

3.1.1

Patch Changes

3.1.0

Minor Changes

3.0.5

Patch Changes

3.0.4

Patch Changes

3.0.3

Patch Changes

3.0.2

Patch Changes

3.0.1

Patch Changes

3.0.0

Major Changes

2.0.2

Patch Changes

2.0.1

Patch Changes

2.0.0

Major Changes

Patch Changes

2.0.0-beta.1

See changes in 2.0.0-beta.1

Patch Changes

2.0.0-beta.0

See changes in 2.0.0-beta.0

Major Changes

1.2.4

Patch Changes

1.2.3

Patch Changes

1.2.2

Patch Changes

1.2.1

Patch Changes

1.2.0

Minor Changes

  • #5088 040837628 Thanks @natemoo-re! - Introducing your new automated assistant: Houston! 🎉

    ╭─────╮  Houston:
│ ◠ ◡ ◠  Initiating launch sequence... right... now!
╰─────╯

    Updates template and TypeScript prompts for clarity and friendliness.

    Migrates template copying from degit (unmaintained) to giget for stability.

1.1.0

Minor Changes

  • #4810 7481ffda0 Thanks @mrienstra! - Always write chosen config to tsconfig.json.
    • Before: Only when strict & strictest was selected
    • After: Also when base is selected (via "Relaxed" or "I prefer not to use TypeScript")

1.0.2

Patch Changes

1.0.1

Patch Changes

1.0.1-next.0

Patch Changes

1.0.0

Major Changes

0.15.1

Patch Changes

0.15.0

Minor Changes

0.14.3

Patch Changes

  • #4075 cc10a5c8e Thanks @Princesseuh! - Added better error handling when cancelling operations, providing bad templates and when there's a degit cache issue

0.14.2

Patch Changes

0.14.1

Patch Changes

0.14.0

Minor Changes

  • #3914 b48767985 Thanks @ran-dall! - Rollback supported node@16 version. Minimum versions are now node@14.20.0 or node@16.14.0.

0.13.0

Minor Changes

  • #3871 1cc5b7890 Thanks @natemoo-re! - Update supported node versions. Minimum versions are now node@14.20.0 or node@16.16.0.

Patch Changes

0.12.5

Patch Changes

0.12.4

Patch Changes

0.12.3

Patch Changes

0.12.2

Patch Changes

0.12.1

Patch Changes

  • #3313 1a5335ed Thanks @bholmesdev! - Update "next steps" with more informative text on each CLI command. Oh, and gradients. A lot more gradients.

0.12.0

Minor Changes

  • #3227 c8f5fa35 Thanks @bholmesdev! - Add "initialize git repository" step to simplify our next steps suggestion. We now give you a one-liner to easily paste in your terminal and start the dev server!

0.11.0

Minor Changes

  • #3223 b7cd6958 Thanks @bholmesdev! - Replace the component framework selector with a new "run astro add" option. This unlocks integrations beyond components during your create-astro setup, including TailwindCSS and Partytown. This also replaces our previous "starter" template with a simplified "Just the basics" option.

0.10.1

Patch Changes

0.10.0

Minor Changes

  • #3190 38e5e9e9 Thanks @bholmesdev! - Feat: add option to install dependencies during setup. This respects the package manager used to run create-astro (ex. "yarn create astro" vs "pnpm create astro@latest").

0.9.0

Minor Changes

  • #3168 7c49194c Thanks @bholmesdev! - Add prompt to choose a directory, now defaulting to a separate "./my-astro-site" instead of "." (current directory)

0.8.0

Minor Changes

  • #2843 1fdb63b5 Thanks @JuanM04! - Automatically add integration peerDependencies to scaffolded package.json files

0.8.0-next.0

Minor Changes

  • #2843 1fdb63b5 Thanks @JuanM04! - Automatically add integration peerDependencies to scaffolded package.json files

0.7.1

Patch Changes

  • #2429 fda857eb Thanks @Mikkel-T! - Added an option to create-astro to use verbose logging which should help debug degit issues

0.7.0

Minor Changes

0.6.10

Patch Changes

0.6.9

Patch Changes

0.6.8

Patch Changes

  • 3e1bdb1a: Add a helpful message for the "could not find commit hash for ..." error

0.6.7

0.6.7-next.1

Patch Changes

  • 6c66d483: Fix issue with v7.x+ versions of npm init, which changed default flag handling

0.6.7-next.0

Patch Changes

  • 6c66d483: Fix issue with v7.x+ versions of npm init, which changed default flag handling

0.6.6

Patch Changes

  • d5fdeefe: Changes create-astro to pull examples from the latest branch

0.6.5

Patch Changes

  • 025f5e3f: Fix to revert change pointing create-astro at the latest branch

0.6.4

Patch Changes

  • 28f00566: Updates create-astro to use the latest branch

0.6.3

Patch Changes

  • 0eeb2534: change rm to unlink for node 12 compatibility

0.6.2

Patch Changes

  • 11a6f884: Added a check to see if the renderers array is empty and only show the message about using the templates default renderers if it isn't

0.6.1

Patch Changes

  • 24dce41c: Adds a new template 'minimal' which does not include a framework

0.6.0

Minor Changes

  • cf4c97cf: forced degit template extraction in case of non empty installation directory

0.5.2

Patch Changes

  • 6c52c92: Add warning when encountering 'zlib: unexpected end of file' error

0.5.1

Patch Changes

  • a7e6666: compile javascript to target Node v12.x
  • bd18e14: Add support for Solid
  • d45431d: create-astro does not fail when removing subdirectories

0.5.1-next.1

Patch Changes

0.5.1-next.0

Patch Changes

  • a7e6666: compile javascript to target Node v12.x
  • d45431d: create-astro does not fail when removing subdirectories

0.5.0

Minor Changes

  • 36e104b: Use new client: prefix for component examples

0.4.0

Minor Changes

  • 5d5d67c: Update create-astro to handle framework-specific logic based on user preference

0.3.5

Patch Changes

  • d8ceff5: Allows using an external repo as a template

    You can do this with the --template flag:

    npm init astro my-shopify --template cassidoo/shopify-react-astro

0.3.4

Patch Changes

0.3.3

Patch Changes

  • f9f2da4: Add repository key to package.json for create-astro

0.3.2

Patch Changes

  • ab2972b: Update package.json engines for esm support

0.3.1

Patch Changes

  • d6a7349: fix issue with empty prompt

0.3.0

Minor Changes