chore(deps): bump the prod-deps group with 3 updates

[dependabot]

Updates the requirements on astro, caniuse-lite and preact to permit the latest version.
Updates astro to 5.1.0

Release notes

Sourced from astro's releases.

[email protected]

Minor Changes

• #12441 b4fec3c Thanks @​ascorbic! - Adds experimental session support

  Sessions are used to store user state between requests for server-rendered pages, such as login status, shopping cart contents, or other user-specific data.

  ---
  export const prerender = false; // Not needed in 'server' mode
  const cart = await Astro.session.get('cart');
  ---
  <a href="/checkout">🛒 {cart?.length ?? 0} items</a>

  Sessions are available in on-demand rendered/SSR pages, API endpoints, actions and middleware. To enable session support, you must configure a storage driver.

  If you are using the Node.js adapter, you can use the fs driver to store session data on the filesystem:

  // astro.config.mjs
  {
    adapter: node({ mode: 'standalone' }),
    experimental: {
      session: {
        // Required: the name of the unstorage driver
        driver: "fs",
      },
    },
  }

  If you are deploying to a serverless environment, you can use drivers such as redis, netlify-blobs, vercel-kv, or cloudflare-kv-binding and optionally pass additional configuration options.

  For more information, including using the session API with other adapters and a full list of supported drivers, see the docs for experimental session support. For even more details, and to leave feedback and participate in the development of this feature, the Sessions RFC.

• #12426 3dc02c5 Thanks @​oliverlynch! - Improves asset caching of remote images

  Astro will now store entity tags and the Last-Modified date for cached remote images and use them to revalidate the cache when it goes stale.

• #12721 c9d5110 Thanks @​florian-lefebvre! - Adds a new getActionPath() helper available from astro:actions

  Astro 5.1 introduces a new helper function, getActionPath() to give you more flexibility when calling your action.

  Calling getActionPath() with your action returns its URL path so you can make a fetch() request with custom headers, or use your action with an API such as navigator.sendBeacon(). Then, you can handle the custom-formatted returned data as needed, just as if you had called an action directly.

  This example shows how to call a defined like action passing the Authorization header and the keepalive option:

... (truncated)

Changelog

Sourced from astro's changelog.

5.1.0

Minor Changes

• #12441 b4fec3c Thanks @​ascorbic! - Adds experimental session support

  Sessions are used to store user state between requests for server-rendered pages, such as login status, shopping cart contents, or other user-specific data.

  ---
  export const prerender = false; // Not needed in 'server' mode
  const cart = await Astro.session.get('cart');
  ---
  <a href="/checkout">🛒 {cart?.length ?? 0} items</a>

  Sessions are available in on-demand rendered/SSR pages, API endpoints, actions and middleware. To enable session support, you must configure a storage driver.

  If you are using the Node.js adapter, you can use the fs driver to store session data on the filesystem:

  // astro.config.mjs
  {
    adapter: node({ mode: 'standalone' }),
    experimental: {
      session: {
        // Required: the name of the unstorage driver
        driver: "fs",
      },
    },
  }

  If you are deploying to a serverless environment, you can use drivers such as redis, netlify-blobs, vercel-kv, or cloudflare-kv-binding and optionally pass additional configuration options.

  For more information, including using the session API with other adapters and a full list of supported drivers, see the docs for experimental session support. For even more details, and to leave feedback and participate in the development of this feature, the Sessions RFC.

• #12426 3dc02c5 Thanks @​oliverlynch! - Improves asset caching of remote images

  Astro will now store entity tags and the Last-Modified date for cached remote images and use them to revalidate the cache when it goes stale.

• #12721 c9d5110 Thanks @​florian-lefebvre! - Adds a new getActionPath() helper available from astro:actions

  Astro 5.1 introduces a new helper function, getActionPath() to give you more flexibility when calling your action.

  Calling getActionPath() with your action returns its URL path so you can make a fetch() request with custom headers, or use your action with an API such as navigator.sendBeacon(). Then, you can handle the custom-formatted returned data as needed, just as if you had called an action directly.

  This example shows how to call a defined like action passing the Authorization header and the keepalive option:

... (truncated)

Commits

• 3f557b2 [ci] release (#12762)
• 4353fc5 fix: correctly return 404.astro in i18n (#12764)
• 45005a5 [ci] format
• 1ec5b44 chore(deps): update unstorage and use new syntax (#12783)
• 45c3f33 [ci] format
• c9d5110 feat(actions): getActionPath() (#12721)
• 36c1e06 fix: clear the content layer cache when the Astro config changes (#12767)
• a581c15 [ci] format
• a94e309 [ci] format
• b4fec3c Sessions API (#12441)
• Additional commits viewable in compare view

Updates caniuse-lite to 1.0.30001690

Commits

• c525df1 Update caniuse-db 1.0.30001690
• See full diff in compare view

Updates preact to 10.25.3

Release notes

Sourced from preact's releases.

10.25.3

Fixes

• Wrap hydration debug message node types in quotes (#4609, thanks @​rschristian)
• Revert "Improve performance and reduce memory allocation" (#4611, thanks @​JoviDeCroock)

Types

• Add default event target types for HTML attribute interfaces (#4606, thanks @​rschristian)

Commits

• 3972db1 10.25.3 (#4612)
• 0023670 Revert "Improve performance and reduce memory allocation" (#4611)
• bb68456 fix: Wrap hydration debug message vars in quotes (#4609)
• 2b82799 refactor: Add default event target types for HTML attribute interfaces (#4606)
• See full diff 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions