Add test for astro:route:setup hook

[Fryuni]

Changes

• Add a test for the new astro:route:setup hook introduced on Deprecates exporting prerender with dynamic values #11657

To ensure it doesn't break with future work regarding routing and route data.

Testing

It's the entire PR 😜

[changeset-bot]

⚠️ No Changeset found

Latest commit: a6465c2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

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

[bluwy]

I'm not really sure this is a usecase we want to explicitly support and test for. It's kinda hacky where you're collecting routes (which doesn't work well in dev because routes can be updated), and the data is saved to globalThis and shared to the endpoint (which will only work if that endpoint is prerendered). I think if you're doing something like that, you'd be accepting some risk that it'll break one day.

[Fryuni]

The test is not for how it is being used, it is just to test that the value is called correctly.

It is just a safeguard for the changes planned for v5 and RFCs regarding routing and RouteData.
Even if some change does break the particular implementation of the test, it is better than silently breaking the behavior for integrations.

[bluwy]

I guess I'm confused that we already had a test in #11657, but it's in @astrojs/node which we're moving it to another repo.

In that case, could we simplify the test that injects an integration inline at here so that it tracks the route in a variable within the describe block? That way we're not relying on globalThis for the tests.