Bump esbuild, @astrojs/mdx, @astrojs/react and astro

[dependabot]

Bumps esbuild to 0.25.11 and updates ancestor dependencies esbuild, @astrojs/mdx, @astrojs/react and astro. These dependencies need to be updated together.

Updates esbuild from 0.21.5 to 0.25.11

Release notes

Sourced from esbuild's releases.

v0.25.11

• Add support for with { type: 'bytes' } imports (#4292)

  The import bytes proposal has reached stage 2.7 in the TC39 process, which means that although it isn't quite recommended for implementation, it's generally approved and ready for validation. Furthermore it has already been implemented by Deno and Webpack. So with this release, esbuild will also add support for this. It behaves exactly the same as esbuild's existing binary loader. Here's an example:

  import data from './image.png' with { type: 'bytes' }
  const view = new DataView(data.buffer, 0, 24)
  const width = view.getInt32(16)
  const height = view.getInt32(20)
  console.log('size:', width + '\xD7' + height)

• Lower CSS media query range syntax (#3748, #4293)

  With this release, esbuild will now transform CSS media query range syntax into equivalent syntax using min-/max- prefixes for older browsers. For example, the following CSS:

  @media (640px <= width <= 960px) {
    main {
      display: flex;
    }
  }

  will be transformed like this with a target such as --target=chrome100 (or more specifically with --supported:media-range=false if desired):

  @media (min-width: 640px) and (max-width: 960px) {
    main {
      display: flex;
    }
  }

v0.25.10

• Fix a panic in a minification edge case (#4287)

  This release fixes a panic due to a null pointer that could happen when esbuild inlines a doubly-nested identity function and the final result is empty. It was fixed by emitting the value undefined in this case, which avoids the panic. This case must be rare since it hasn't come up until now. Here is an example of code that previously triggered the panic (which only happened when minifying):

  function identity(x) { return x }
  identity({ y: identity(123) })

• Fix @supports nested inside pseudo-element (#4265)

  When transforming nested CSS to non-nested CSS, esbuild is supposed to filter out pseudo-elements such as ::placeholder for correctness. The CSS nesting specification says the following:

  The nesting selector cannot represent pseudo-elements (identical to the behavior of the ':is()' pseudo-class). We’d like to relax this restriction, but need to do so simultaneously for both ':is()' and '&', since they’re intentionally built on the same underlying mechanisms.

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2024

This changelog documents all esbuild versions published in the year 2024 (versions 0.19.12 through 0.24.2).

0.24.2

• Fix regression with --define and import.meta (#4010, #4012, #4013)

  The previous change in version 0.24.1 to use a more expression-like parser for define values to allow quoted property names introduced a regression that removed the ability to use --define:import.meta=.... Even though import is normally a keyword that can't be used as an identifier, ES modules special-case the import.meta expression to behave like an identifier anyway. This change fixes the regression.

  This fix was contributed by @​sapphi-red.

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:

... (truncated)

Commits

• 6b7c4f2 publish 0.25.11 to npm
• 7295c1a css: also parse media queries in @import rules
• e3991dd css: some adjustments to @import parsing
• 8bb82ca fix #3748, fix #4293: lower css media range syntax
• d8c3f87 css: parse and print media queries
• 6e75bc7 run make update-compat-table
• 8f506d5 fix #4292: support with { type: bytes }
• d6b668f publish 0.25.10 to npm
• 5088c19 refactor: use strings.Builder (#4290)
• 755da31 run make update-compat-table
• Additional commits viewable in compare view

Updates @astrojs/mdx from 1.1.5 to 4.3.7

Release notes

Sourced from @​astrojs/mdx's releases.

@​astrojs/mdx@​4.3.7

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@​6.3.8

@​astrojs/mdx@​4.3.6

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@​6.3.7

@​astrojs/mdx@​4.3.5

Patch Changes

• #14326 c24a8f4 Thanks @​jsparkdev! - Updates vite version to fix CVE

@​astrojs/mdx@​4.3.4

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@​6.3.6

@​astrojs/mdx@​4.3.3

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@​6.3.5

@​astrojs/mdx@​4.3.2

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@​6.3.4

Changelog

Sourced from @​astrojs/mdx's changelog.

4.3.7

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@​6.3.8

4.3.6

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@​6.3.7

4.3.5

Patch Changes

• #14326 c24a8f4 Thanks @​jsparkdev! - Updates vite version to fix CVE

4.3.4

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@​6.3.6

4.3.3

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@​6.3.5

4.3.2

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@​6.3.4

4.3.1

Patch Changes

• Updated dependencies [6bd5f75]:
  • @​astrojs/markdown-remark@​6.3.3

4.3.0

... (truncated)

Commits

• 3bb14b7 [ci] release (#14466)
• 29ff12f [ci] release (#14416)
• aa7bebd [ci] release (#14295)
• c24a8f4 fix(vite): update vite to fix CVE (#14326)
• 42a2cc5 fix(deps): update astro dependencies (#14307)
• bdc8ce2 fix(deps): update astro dependencies (#14305)
• 9288133 [ci] release (#14232)
• 0f0a4c4 [ci] release (#14172)
• 5eaf524 [ci] release (#14171)
• 9cfccc7 [ci] format
• Additional commits viewable in compare view

Updates @astrojs/react from 3.6.3 to 4.4.0

Release notes

Sourced from @​astrojs/react's releases.

@​astrojs/react@​4.4.0

Minor Changes

• #14386 f75f446 Thanks @​yanthomasdev! - Stabilizes the formerly experimental getActionState() and withState() functions introduced in @astrojs/react v3.4.0 used to integrate Astro Actions with React 19's useActionState() hook.

  This example calls a like action that accepts a postId and returns the number of likes. Pass this action to the withState() function to apply progressive enhancement info, and apply to useActionState() to track the result:

  import { actions } from 'astro:actions';
  import { withState } from '@astrojs/react/actions';
  import { useActionState } from 'react';
  export function Like({ postId }: { postId: string }) {
  const [state, action, pending] = useActionState(
  withState(actions.like),
  0, // initial likes
  );
  return (
  <form action={action}>
  <input type="hidden" name="postId" value={postId} />
  <button disabled={pending}>{state} ❤️</button>
  </form>
  );
  }
  

  You can also access the state stored by useActionState() from your action handler. Call getActionState() with the API context, and optionally apply a type to the result:

  import { defineAction } from 'astro:actions';
  import { z } from 'astro:schema';
  import { getActionState } from '@astrojs/react/actions';
  export const server = {
  like: defineAction({
  input: z.object({
  postId: z.string(),
  }),
  handler: async ({ postId }, ctx) => {
  const currentLikes = getActionState<number>(ctx);
  // write to database
  return currentLikes + 1;
  },
  }),
  };
  

  If you were previously using this experimental feature, you will need to update your code to use the new stable exports:

  // src/components/Form.jsx
  import { actions } from 'astro:actions';
  -import { experimental_withState } from '@astrojs/react/actions';

... (truncated)

Changelog

Sourced from @​astrojs/react's changelog.

4.4.0

Minor Changes

• #14386 f75f446 Thanks @​yanthomasdev! - Stabilizes the formerly experimental getActionState() and withState() functions introduced in @astrojs/react v3.4.0 used to integrate Astro Actions with React 19's useActionState() hook.

  This example calls a like action that accepts a postId and returns the number of likes. Pass this action to the withState() function to apply progressive enhancement info, and apply to useActionState() to track the result:

  import { actions } from 'astro:actions';
  import { withState } from '@astrojs/react/actions';
  import { useActionState } from 'react';
  export function Like({ postId }: { postId: string }) {
  const [state, action, pending] = useActionState(
  withState(actions.like),
  0, // initial likes
  );
  return (
  <form action={action}>
  <input type="hidden" name="postId" value={postId} />
  <button disabled={pending}>{state} ❤️</button>
  </form>
  );
  }
  

  You can also access the state stored by useActionState() from your action handler. Call getActionState() with the API context, and optionally apply a type to the result:

  import { defineAction } from 'astro:actions';
  import { z } from 'astro:schema';
  import { getActionState } from '@astrojs/react/actions';
  export const server = {
  like: defineAction({
  input: z.object({
  postId: z.string(),
  }),
  handler: async ({ postId }, ctx) => {
  const currentLikes = getActionState<number>(ctx);
  // write to database
  return currentLikes + 1;
  },
  }),
  };
  

  If you were previously using this experimental feature, you will need to update your code to use the new stable exports:

... (truncated)

Commits

• 731c07d [ci] release (#14434)
• a98ce3c [ci] format
• f75f446 Stabilize React 19 + Actions APIs (#14386)
• aa7bebd [ci] release (#14295)
• c24a8f4 fix(vite): update vite to fix CVE (#14326)
• 0b0d9ed fix(deps): update astro client runtimes (#14184)
• 540f27e fix(deps): update astro client runtimes (#14024)
• 9cfccc7 [ci] format
• 33f2d15 chore: upgrade to Biome v2 (#13984)
• f1ac805 fix(deps): update astro client runtimes (#13912)
• Additional commits viewable in compare view

Updates astro from 3.6.5 to 5.14.5

Release notes

Sourced from astro's releases.

astro@5.14.5

Patch Changes

• #14525 4f55781 Thanks @​penx! - Fixes defineLiveCollection() types

• #14441 62ec8ea Thanks @​upsuper! - Updates redirect handling to be consistent across static and server output, aligning with the behavior of other adapters.

  Previously, the Node.js adapter used default HTML files with meta refresh tags when in static output. This often resulted in an extra flash of the page on redirect, while also not applying the proper status code for redirections. It's also likely less friendly to search engines.

  This update ensures that configured redirects are always handled as HTTP redirects regardless of output mode, and the default HTML files for the redirects are no longer generated in static output. It makes the Node.js adapter more consistent with the other official adapters.

  No change to your project is required to take advantage of this new adapter functionality. It is not expected to cause any breaking changes. However, if you relied on the previous redirecting behavior, you may need to handle your redirects differently now. Otherwise you should notice smoother redirects, with more accurate HTTP status codes, and may potentially see some SEO gains.

• #14506 ec3cbe1 Thanks @​abdo-spices! - Updates the <Font /> component so that preload links are generated after the style tag, as recommended by capo.js

astro@5.14.4

Patch Changes

• #14509 7e04caf Thanks @​ArmandPhilippot! - Fixes an error in the docs that specified an incorrect version for the security.allowedDomains release.

astro@5.14.3

Patch Changes

• #14505 28b2a1d Thanks @​matthewp! - Fixes Cannot set property manifest error in test utilities by adding a protected setter for the manifest property

• #14235 c4d84bb Thanks @​toxeeec! - Fixes a bug where the "tap" prefetch strategy worked only on the first clicked link with view transitions enabled

astro@5.14.1

Patch Changes

• #14440 a3e16ab Thanks @​florian-lefebvre! - Fixes a case where the URLs generated by the experimental Fonts API would be incorrect in dev

astro@5.14.0

Minor Changes

• #13520 a31edb8 Thanks @​openscript! - Adds a new property routePattern available to GetStaticPathsOptions

  This provides the original, dynamic segment definition in a routing file path (e.g. /[...locale]/[files]/[slug]) from the Astro render context that would not otherwise be available within the scope of getStaticPaths(). This can be useful to calculate the params and props for each page route.

  For example, you can now localize your route segments and return an array of static paths by passing routePattern to a custom getLocalizedData() helper function. The params object will be set with explicit values for each route segment (e.g. locale, files, and slug). Then, these values will be used to generate the routes and can be used in your page template via Astro.params.

  // src/pages/[...locale]/[files]/[slug].astro
  import { getLocalizedData } from "../../../utils/i18n"; export async function getStaticPaths({ routePattern
  }) { const response = await fetch('...'); const data = await response.json(); console.log(routePattern);
  // [...locale]/[files]/[slug] // Call your custom helper with routePattern to generate the static
  paths return data.flatMap((file) => getLocalizedData(file, routePattern)); } const { locale, files,
  slug } = Astro.params;

... (truncated)

Changelog

Sourced from astro's changelog.

5.14.5

Patch Changes

• #14525 4f55781 Thanks @​penx! - Fixes defineLiveCollection() types

• #14441 62ec8ea Thanks @​upsuper! - Updates redirect handling to be consistent across static and server output, aligning with the behavior of other adapters.

  Previously, the Node.js adapter used default HTML files with meta refresh tags when in static output. This often resulted in an extra flash of the page on redirect, while also not applying the proper status code for redirections. It's also likely less friendly to search engines.

  This update ensures that configured redirects are always handled as HTTP redirects regardless of output mode, and the default HTML files for the redirects are no longer generated in static output. It makes the Node.js adapter more consistent with the other official adapters.

  No change to your project is required to take advantage of this new adapter functionality. It is not expected to cause any breaking changes. However, if you relied on the previous redirecting behavior, you may need to handle your redirects differently now. Otherwise you should notice smoother redirects, with more accurate HTTP status codes, and may potentially see some SEO gains.

• #14506 ec3cbe1 Thanks @​abdo-spices! - Updates the <Font /> component so that preload links are generated after the style tag, as recommended by capo.js

5.14.4

Patch Changes

• #14509 7e04caf Thanks @​ArmandPhilippot! - Fixes an error in the docs that specified an incorrect version for the security.allowedDomains release.

5.14.3

Patch Changes

• #14505 28b2a1d Thanks @​matthewp! - Fixes Cannot set property manifest error in test utilities by adding a protected setter for the manifest property

• #14235 c4d84bb Thanks @​toxeeec! - Fixes a bug where the "tap" prefetch strategy worked only on the first clicked link with view transitions enabled

5.14.2

Patch Changes

• #14459 916f9c2 Thanks @​florian-lefebvre! - Improves font files URLs in development when using the experimental fonts API by showing the subset if present

• b8ca69b Thanks @​ascorbic! - Aligns dev image server file base with Vite rules

• #14469 1c090b0 Thanks @​delucis! - Updates tinyexec dependency

• #14460 008dc75 Thanks @​florian-lefebvre! - Fixes a case where astro:config/server values typed as URLs would be serialized as strings

• #13730 7260367 Thanks @​razonyang! - Fixes a bug in i18n, where Astro caused an infinite loop when a locale that doesn't have an index, and Astro falls back to the index of the default locale.

• 6ee63bf Thanks @​matthewp! - Adds security.allowedDomains configuration to validate X-Forwarded-Host headers in SSR

  The X-Forwarded-Host header will now only be trusted if it matches one of the configured allowed host patterns. This prevents host header injection attacks that can lead to cache poisoning and other security vulnerabilities.

  Configure allowed host patterns to enable X-Forwarded-Host support:

... (truncated)

Commits

• ef7af66 [ci] release (#14527)
• 62ec8ea feat(node): handle redirects dynamically in static mode (#14441)
• 4f55781 Update content.d.ts astro/loader => loaders (#14525)
• cd30254 refactor(cli): create-key (#14501)
• ec3cbe1 refactor(Font.astro) reorder Font.astro content based on capo.js (#14506)
• 3a3a7fe fix heading level in config reference docs (#14517)
• 3412859 [ci] release (#14510)
• 7e04caf docs: fix security.allowedDomains version (#14509)
• fe1d35c [ci] release (#14507)
• 7926882 [ci] format
• 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 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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.