Add template tsconfigs for users to extend from

[Princesseuh]

Changes

This adds tsconfig templates that users can extend from and update our templates and create-astro to use them. The benefits of having those templates is that it's neater, convenient for users to build from and that we can update them between versions of Astro without needing any users interaction (ex: adding new TypeScript settings, setting up aliases etc)

This also severely reduce the maintenance cost of our templates since we don't have to update all the tsconfig.json manually anymore

Fix #4297 at the same time

Testing

Tested manually

Docs

N/A

[changeset-bot]

🦋 Changeset detected

Latest commit: 2312699

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

This PR includes changesets to release 15 packages

Name	Type
astro	Patch
create-astro	Patch
@e2e/astro-component	Patch
@e2e/error-react-spectrum	Patch
@e2e/error-sass	Patch
@e2e/errors	Patch
@e2e/hydration-race	Patch
@e2e/lit-component	Patch
@e2e/preact-component	Patch
@e2e/react-component	Patch
@e2e/solid-component	Patch
@e2e/solid-recurse	Patch
@e2e/svelte-component	Patch
@e2e/e2e-tailwindcss	Patch
@e2e/ts-resolution	Patch

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

[Princesseuh]

Hmm, this works perfectly fine in the editor, but for some reason Vite/ESBuild isn't able to resolve the extends and building fails. Not sure why

[Princesseuh]

We need those two because in a tsconfig.json, you can optionally omit the file extension

[FredKSchott]

Are we ready for tsconfig changes to become breaking changes? This will really limit changes to these files going forward, so I just want to call that out. If we think this is stable enough to not really change until v2.0, then I'm on board!

[Princesseuh]

Are we ready for tsconfig changes to become breaking changes? This will really limit changes to these files going forward, so I just want to call that out. If we think this is stable enough to not really change until v2.0, then I'm on board!

That's good to me! I honestly don't expect much breaking changes to them in our future. The big one that could come to mind would be switching to moduleResolution: 'node16' at some point, perhaps? Apart from that, our changes should be synced with TypeScript releases, which makes them easier to justify

[FredKSchott]

SGTM!