Add server island metadata

[matthewp]

Changes

• Discovers server:defer directive usage, then links that back to the import statement like what is done with client: islands. This information is exported as part of the compile result, on the serverComponents field, to be used by Astro.

Testing

• Since the only visible change is to the metadata, this is tested by adding a wasm test, to verify that the information is included and is correct.

Docs

N/A

[changeset-bot]

🦋 Changeset detected

Latest commit: 36c0339

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

This PR includes changesets to release 1 package

Name	Type
@astrojs/compiler	Minor

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

[matthewp]

!preview server-islands

[github-actions]

 > [email protected] release /home/runner/work/compiler/compiler > changeset publish "--tag" "next--server-islands" 🦋 warn ===============================IMPORTANT!=============================== 🦋 warn Packages will be released under the next--server-islands tag 🦋 warn ---------------------------------------------------------------------- 🦋 info npm info @astrojs/compiler 🦋 info @astrojs/compiler is being published because our local version (0.0.0-server-islands-20240610194904) has not been published on npm 🦋 info Publishing "@astrojs/compiler" at "0.0.0-server-islands-20240610194904" 🦋 success packages published successfully: 🦋 @astrojs/[email protected] 🦋 Creating git tag... 🦋 New tag: @astrojs/[email protected]

[matthewp]

!preview server-islands

[github-actions]

 > [email protected] release /home/runner/work/compiler/compiler > changeset publish "--tag" "next--server-islands" 🦋 warn ===============================IMPORTANT!=============================== 🦋 warn Packages will be released under the next--server-islands tag 🦋 warn ---------------------------------------------------------------------- 🦋 info npm info @astrojs/compiler 🦋 info @astrojs/compiler is being published because our local version (0.0.0-server-islands-20240619175952) has not been published on npm 🦋 info Publishing "@astrojs/compiler" at "0.0.0-server-islands-20240619175952" 🦋 success packages published successfully: 🦋 @astrojs/[email protected] 🦋 Creating git tag... 🦋 New tag: @astrojs/[email protected]

[matthewp]

!preview server-islands

[github-actions]

 > [email protected] release /home/runner/work/compiler/compiler > changeset publish "--tag" "next--server-islands" 🦋 warn ===============================IMPORTANT!=============================== 🦋 warn Packages will be released under the next--server-islands tag 🦋 warn ---------------------------------------------------------------------- 🦋 info npm info @astrojs/compiler 🦋 info @astrojs/compiler is being published because our local version (0.0.0-server-islands-20240620184241) has not been published on npm 🦋 info Publishing "@astrojs/compiler" at "0.0.0-server-islands-20240620184241" 🦋 success packages published successfully: 🦋 @astrojs/[email protected] 🦋 Creating git tag... 🦋 New tag: @astrojs/[email protected]

[ematipico]

Can you also create some snapshot tests in the go testing suite? It would be nice to have some safety against regressions

[matthewp]

@ematipico this doesn't change the compiled output JS at all. It just adds the metadata that's only retrieved from the JS compiler API. That's why the tests are there.

[Princesseuh]

Code looks good to me!