chore(deps): bump the minor group in /docs with 5 updates

[dependabot]

Bumps the minor group in /docs with 5 updates:

Package	From	To
astro	5.0.9	5.1.0
@esbuild/openbsd-arm64	0.24.0	0.24.1
chokidar	4.0.3	3.6.0
detect-libc	2.0.3	1.0.3
readdirp	4.0.2	3.6.0

Updates astro from 5.0.9 to 5.1.0

Release notes

Sourced from astro's releases.

astro@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)

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 @esbuild/openbsd-arm64 from 0.24.0 to 0.24.1

Release notes

Sourced from @​esbuild/openbsd-arm64's releases.

v0.24.1

• Allow es2024 as a target in tsconfig.json (#4004)

  TypeScript recently added es2024 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:

  {
    "compilerOptions": {
      "target": "ES2024"
    }
  }

  As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.

  This fix was contributed by @​billyjanitsch.

• Allow automatic semicolon insertion after get/set

  This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:

  class Foo {
    get
    *x() {}
    set
    *y() {}
  }

  The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.

• Allow quoted property names in --define and --pure (#4008)

  The define and pure API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes --define and --pure consistent with --global-name, which already supported quoted property names. For example, the following is now possible:

  // The following code now transforms to "return true;\n"
  console.log(esbuild.transformSync(
    `return process.env['SOME-TEST-VAR']`,
    { define: { 'process.env["SOME-TEST-VAR"]': 'true' } },
  ))

  Note that if you're passing values like this on the command line using esbuild's --define flag, then you'll need to know how to escape quote characters for your shell. You may find esbuild's JavaScript API more ergonomic and portable than writing shell code.

• Minify empty try/catch/finally blocks (#4003)

  With this release, esbuild will now attempt to minify empty try blocks:

... (truncated)

Changelog

Sourced from @​esbuild/openbsd-arm64's changelog.

0.24.1

• Allow es2024 as a target in tsconfig.json (#4004)

  TypeScript recently added es2024 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:

  {
    "compilerOptions": {
      "target": "ES2024"
    }
  }

  As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.

  This fix was contributed by @​billyjanitsch.

• Allow automatic semicolon insertion after get/set

  This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:

  class Foo {
    get
    *x() {}
    set
    *y() {}
  }

  The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.

• Allow quoted property names in --define and --pure (#4008)

  The define and pure API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes --define and --pure consistent with --global-name, which already supported quoted property names. For example, the following is now possible:

  // The following code now transforms to "return true;\n"
  console.log(esbuild.transformSync(
    `return process.env['SOME-TEST-VAR']`,
    { define: { 'process.env["SOME-TEST-VAR"]': 'true' } },
  ))

  Note that if you're passing values like this on the command line using esbuild's --define flag, then you'll need to know how to escape quote characters for your shell. You may find esbuild's JavaScript API more ergonomic and portable than writing shell code.

• Minify empty try/catch/finally blocks (#4003)

  With this release, esbuild will now attempt to minify empty try blocks:

... (truncated)

Commits

• de9598f publish 0.24.1 to npm
• 15d56ca emit null source mappings for empty chunk content
• 8d98f6f fix #3985: entryPoint metadata for copy loader
• 0db1b82 fix #3998: avoid outbase in identifier names
• 7236472 close #3974: add support for netbsd on arm64
• 3ae3525 fix #3990: add credit for the es2024 change
• 88977cc run make update-compat-table and fix breakages
• fd4cea7 fix #4008: allow quoted define and pure names
• 68573ab internal: factor out key format for define map
• 364e5b9 internal: remove the separate DotDefine struct
• Additional commits viewable in compare view

Updates chokidar from 4.0.3 to 3.6.0

Commits

• 7c50e25 Release 3.6.0.
• 112015f Add github ci autopublish
• ab12362 Merge pull request #1300 from ben-polinsky/fix-fswatcher-types-1299
• 29a2f13 fix formatting
• a0f9e09 update fs.FSWatcher types to satisfy node versions >= 16; fixes #1299
• 5589454 Merge pull request #1197 from MarcCelani-at/handleMustScanSubDirs
• 399647e Merge pull request #1288 from JLHwung/fix-ready-count
• f022fe7 ready call # is unfortunately platform specific
• 1370123 fix readyCount logic
• 08318d6 Adjust funding field in pkg
• Additional commits viewable in compare view

Updates detect-libc from 2.0.3 to 1.0.3

Commits

• 01fdf51 Reveal detection method and polyfill spawnSync (#5)
• 2507554 Add support for ldd exit code 1 e.g. Alpine 3.6 #2
• 7d75363 Add partial support for Node 0.10 and 0.12
• 4642b20 Release v0.2.0
• 5828dfe Catch and ignore sync ENOENT error
• 0381ad7 Add filesystem-based checks for libc family only #1
• 7b36e34 Release v0.1.0
• f38a4e6 Move 'is non-glibc Linux' logic from bin to lib
• c8609d7 Set LIBC only for non-glibc
• 89d34bf Reduce Travis CI matrix
• Additional commits viewable in compare view

Updates readdirp from 4.0.2 to 3.6.0

Commits

• e353d45 Prettier
• 6ffb4c6 Update check for fs.stat/fs.lstat bigint support. (#171)
• 62eea1a Merge pull request #169 from ath0mas/fix/168-recusive-warn
• 7c31860 Skip with warn for circular symlinks, instead of exit with error (#168)
• 887e9f3 Release 3.5.0.
• a7d43ba Add devdev typescript.
• 59a7970 Changelog
• 6119c44microsoft/vscode#108441
• 6e29e80 Merge pull request #161 from paulmillr/dependabot/npm_and_yarn/types/node-14.0.1
• bbb6a5f Bump @​types/node from 13.13.6 to 14.0.1
• 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 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

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.