Improving Typescript code parsing in Astro components

[MoustaphaDev]

Body

Summary

Explore a more effective approach to parsing frontmatter code in Astro components, particularly when dealing with TypeScript.

Background & Motivation

Currently, the Astro compiler handles TypeScript code (for export/import hoisting and Props type detection purposes, etc) using a JavaScript parser that it extends to support TypeScript. While functional in most cases, it may fall short when dealing with certain TypeScript code, as it's not a fully-fledged TypeScript parser. This limitation is evident in several open issues: withastro/compiler#927, withastro/compiler#554, withastro/compiler#863, withastro/compiler#763, withastro/compiler#878, withastro/compiler#749, withastro/compiler#1056

While patching individual issues is possible, it's unsustainable in the long term, requiring constant maintenance and potentially introducing further incompatibilities.

Goals

• Identify a more robust method for parsing frontmatter code
• Alleviate the maintenance burden associated with extending the current setup to fully handle TypeScript syntax

Unresolved question

• Which TypeScript parser should be used?
• How might the transition impact performance?

[Princesseuh]

That sounds great to me! Not sure if there's many TypeScript parsers in Go, maybe ESBuild's can be used, somehow?

[natemoo-re]

We could certainly investigate forking the ESBuild TypeScript parser, like we did for ESBuild's CSS parser for similar reasons.

Unfortunately the Go ecosystem does not seem to have any mature packages that can parse modern JavaScript/TypeScript. Most are stuck on basic ES2015.

[MoustaphaDev]

Yep we'll probably have to go that route unfortunately, I'm not aware of any proper TS parser in go.