bump(deps): bump astro from 2.8.0 to 2.9.0 in /web

[dependabot]

Bumps astro from 2.8.0 to 2.9.0.

Release notes

Sourced from astro's releases.

astro@2.9.0

Minor Changes

• #7686 ec745d689 Thanks @​matthewp! - Redirects configuration

  This change moves the redirects configuration out of experimental. If you were previously using experimental redirects, remove the following experimental flag:

  experimental: {
    redirects: true,
  }

  If you have been waiting for stabilization before using redirects, now you can do so. Check out the docs on redirects to learn how to use this built-in feature.

• #7707 3a6e42e19 Thanks @​ottomated! - Improved hoisted script bundling

  Astro's static analysis to determine which <script> tags to bundle together just got a little smarter!

  Astro create bundles that optimize script usage between pages and place them in the head of the document so that they are downloaded as early as possible. One limitation to Astro's existing approach has been that you could not dynamically use hoisted scripts. Each page received the same, all-inclusive bundle whether or not every script was needed on that page.

  Now, Astro has improved the static analysis to take into account the actual imports used.

  For example, Astro would previously bundle the <script>s from both the <Tab> and <Accordian> component for the following library that re-exports multiple components:

  @​matthewp/my-astro-lib

  export { default as Tabs } from './Tabs.astro';
  export { default as Accordion } from './Accordion.astro';

  Now, when an Astro page only uses a single component, Astro will send only the necessary script to the page. A page that only imports the <Accordian> component will not receive any <Tab> component's scripts:

  ---
  import { Accordion } from '@matthewp/my-astro-lib';
  ---

  You should now see more efficient performance with Astro now supporting this common library re-export pattern.

• #7511 6a12fcecb Thanks @​matthewp! - Built-in View Transitions Support (experimental)

  Astro now supports view transitions through the new <ViewTransitions /> component and the transition:animate (and associated) directives. View transitions are a great fit for content-oriented sites, and we see it as the best path to get the benefits of client-side routing (smoother transitions) without sacrificing the more simple mental model of MPAs.

  Enable support for view transitions in Astro 2.9 by adding the experimental flag to your config:

  import { defineConfig } from 'astro/config';

... (truncated)

Changelog

Sourced from astro's changelog.

2.9.0

Minor Changes

• #7686 ec745d689 Thanks @​matthewp! - Redirects configuration

  This change moves the redirects configuration out of experimental. If you were previously using experimental redirects, remove the following experimental flag:

  experimental: {
    redirects: true,
  }

  If you have been waiting for stabilization before using redirects, now you can do so. Check out the docs on redirects to learn how to use this built-in feature.

• #7707 3a6e42e19 Thanks @​ottomated! - Improved hoisted script bundling

  Astro's static analysis to determine which <script> tags to bundle together just got a little smarter!

  Astro create bundles that optimize script usage between pages and place them in the head of the document so that they are downloaded as early as possible. One limitation to Astro's existing approach has been that you could not dynamically use hoisted scripts. Each page received the same, all-inclusive bundle whether or not every script was needed on that page.

  Now, Astro has improved the static analysis to take into account the actual imports used.

  For example, Astro would previously bundle the <script>s from both the <Tab> and <Accordian> component for the following library that re-exports multiple components:

  @​matthewp/my-astro-lib

  export { default as Tabs } from './Tabs.astro';
  export { default as Accordion } from './Accordion.astro';

  Now, when an Astro page only uses a single component, Astro will send only the necessary script to the page. A page that only imports the <Accordian> component will not receive any <Tab> component's scripts:

  ---
  import { Accordion } from '@matthewp/my-astro-lib';
  ---

  You should now see more efficient performance with Astro now supporting this common library re-export pattern.

• #7511 6a12fcecb Thanks @​matthewp! - Built-in View Transitions Support (experimental)

  Astro now supports view transitions through the new <ViewTransitions /> component and the transition:animate (and associated) directives. View transitions are a great fit for content-oriented sites, and we see it as the best path to get the benefits of client-side routing (smoother transitions) without sacrificing the more simple mental model of MPAs.

  Enable support for view transitions in Astro 2.9 by adding the experimental flag to your config:

... (truncated)

Commits

• 92382ea [ci] release (#7714)
• b4090f8 [ci] format
• 3a6e42e Determine hoisted scripts via AST analysis (#7707)
• 7a26a52 [ci] format
• c102c4a refactor: move dev rendering logic inside vite plugin (#7728)
• d8bae78 Fix organize-imports-cli with satisfies operator (#7727)
• 47c698b [ci] format
• 3043f98 refactor: unify renderPage and callEndpoint in one single function (#7703)
• 30cdc28 [ci] format
• 464eb4f Import missing TransitionAnimationPair (#7726)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)