feat: return clientEntrypoint from getContainerRenderer

[ascorbic]

Changes

Adds clientEntrypoint to the object returned by getContainerRenderer() in framework integrations. This makes the return value an AstroRenderer, so this also deprecates the ContainerRenderer type in favour of that. In several integrations there is already a getRenderer function that returns this, but this isn't standardised, and some need arguments. This PR tries to wrap or re-export these where appropriate.

It seems we were already specifying AstroRenderer as the type passed to loadRenderers, so this doesn't need changing.

The reason to do this is to support client hydration in getContainerRenderer(). The objects returned from these can be used with the loadRenderers helper in a Vite environment, instead of needing users to manually load the correct renderer entrypoints. Previously this didn't return the client entrypoint value, so it required users to manually call container.addClientRenderer() with the appropriate client renderer entrypoint to support hydration.

Testing

Our tests don't use Vitest so we can't test this directly. Instead, I added this to examples/container-with-vitest and tested that.

Docs

The docs don't currently state that client-side hydration is unsupported when using getContainerRenderer, so this doesn't need changing.

[changeset-bot]

🦋 Changeset detected

Latest commit: f7ce94a

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

[ascorbic]

Flipped the logic on this so it works better as a type predicate

[codspeed-hq]

CodSpeed Performance Report

Merging #14715 will not alter performance

_{Comparing container-renderer-client (f7ce94a) with main (a4d284d)}

Summary

✅ 6 untouched