create-astro updates

[Princesseuh]

Changes

This PR includes a few changes to the experience of creating a new project in Astro:

• The list of available templates is now the following:
  • Basics
  • Blog
  • Docs (Starlight)
  • Portfolio
  • In the stable version of Astro 5, Storefront will be added as well
• The TypeScript question has been removed, the default value is now strict for everyone. The presets still exists for anyone wanting a more relaxed or strict experience. Remember, Astro is TypeScript.
  • // @ts-check has been added to all the examples config files
  • astro check is no longer enabled by default for the build command
• create-astro now takes a --add flag, allowing one to add a bunch of integrations in one command.

Basic example rework

The basics template has been reworked to provide a more minimal template, allowing it to serve as a mix between "Basics" and "Minimal":

• The theme of the basics template has been moved into a built-in "Welcome" component exported from Astro directly. The source code of that component is plain .astro, allowing one to still inspect how you'd achieve things in Astro. This component takes in a props to customise the title, still allowing for the implicit teaching of props. A very basic layout (similar to Emmet's doc command) is included, both to setup basic HTML stuff and teach the user about templates / slots

Testing

Added / updated tests

Docs

We'll update the docs:tm:

[changeset-bot]

🦋 Changeset detected

Latest commit: e6425d2

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[TheOtterlord]

Todo:

• Add tests for --add
• Add documentation for --add
• No longer set to output: 'server' when using astro add? (done in feat: makes it so astro add does not set output server by default #12071)

[sarah11918]

Thanks for pinging, Erika!

So, off the top of my head (I'll make a task for myself to follow up):

• We don't need anything in the Upgrade guide since technically this can't break an existing project. I suspect this will either be more of a "discovery" or something to hype for the blog post.

• I will need to update the tutorial that is currently expecting the base TS setting, and the current "minimal" template

• I will check the TypeScript/config pages that describe our settings to make sure nothing expects base and describes updating that

• document the new --add flag

• As much as we can manage (which might not be much depending on our whole sidebar recreation? This might have to be the next quarter project), we can look at updating code examples with Tabs for JS/TS, or showing more TS examples in docs now that we can expect the basic project to use strict and more people to need to avoid squiggles. 😅 I will see if I can wrangle some maintainers/contributors to start prepping for this at least.

[bluwy]

LGTM. Looks like the running the basics template locally causes some dynamic import errors with Vite. But I think that could be investigated separately in the future.